I have been working at cleaning up the Yaml configuration for default table compression settings and found that the CompressedSequentialWriterTest uses some parameters that are outside the acceptable limits (like bufferLength not a power of 2, or maxCompressedLength > bufferLength).
I can understand that these settings were used to set some extreme condition, but shouldn't they be within the max/min ranges? Is it also possible that the tests are not testing what we think they are because of the parameter issue. I have left the code path in place that allows creation of invalid parameters but I am concerned. Claude
