Demonstrate bug for issue #11253

[jkolash]

Show that we do not bound the number of column statistics if the nested struct had 200 columns we would end up with over 200 statistics.

[singhpk234]

@jkolash this is a known behaviour,
The limit is enforced at top level columns
please ref this discussion: #5215 (comment)

[jkolash]

Hmm the purpose of this property is to bound the number of metrics that get created for tables with wide schemas. the fact that it doesn't work with all types of wide schemas seems to be a fundamental flaw. I see the comment

Yes, but this is the current behavior. We use the top-level columns for the current check.
#5215 (comment)

but I don't see an explanation beyond that why it should be limited to top level columns.

[jkolash]

I can close this and open a feature request instead or keep discussion on the issue instead. #11253

let me know

[singhpk234]

I think both works, i would recommend raising this in iceberg slack channel for #dev as well to open up to wider forum !

[jkolash]

Ok I started a slack thread and mailing list discussion I will close this issue for now.