Place limit on fence begin and end row size.

The fence concept provided as part of the no-chop merges places start row and end row data associated with a metadata file reference to fence off sections of files.

There should be an maximum limit on the number of bytes that these values can hold. On possibility may be to use the TABLE_MAX_END_ROW_SIZE property that was introduced in 1.7.0. Currently the default is 10K.

Allowing unbounded values would likely lead to performance issues reading, processing and storing the fence information as it grows larger.

Start by tracing how fence start-row and end-row values are read, processed, and stored for metadata file references, then compare that path with the TABLE_MAX_END_ROW_SIZE property introduced in 1.7.0. Done means both fence row values have a defined maximum and oversized values are handled consistently without unbounded processing or storage.

Written by the indexing model from the issue text.