romandenysov-akv opened a new issue, #22: URL: https://github.com/apache/iceberg-verification/issues/22
Follow-up to apache/iceberg-verification#17 and #12. Expand `table-spec/partition-transforms/bucket/cases.json` with spec-grounded cases for: - `int` values `0` and `-1`; - a negative decimal; - an empty string; - at least one bucket count other than `100`. Add a small script under `dev/` that recomputes bucket expectations from the Iceberg Appendix B type encodings, Murmur3 x86 32-bit with seed 0, and `(hash & Integer.MAX_VALUE) % N`. Document how to run it in the surface README, and cross-check the resulting values against an independent implementation. Include both accepting and rejecting script or validator checks if the new tooling introduces a validation contract. Keep the spec as the source of truth. For pre-epoch nanosecond timestamps between exact microseconds, Appendix B says to convert to microsecond precision but does not specify whether negative fractions round down or toward zero. Raise that question on [email protected] before adding an expected bucket for `1969-12-31T23:59:59.999999999` (or the zoned equivalent). The current PR includes an exact pre-epoch microsecond case that avoids this ambiguity. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
