RussellSpitzer commented on issue #15427: URL: https://github.com/apache/iceberg/issues/15427#issuecomment-3961095602
I think we would probably want to do something at code level via "constraints" because I feel like it's pretty dangerous to introduce normalization as an opt-in that's not supported by all engines. If we did that we could potentially have a client running Iceberg 1.12 that does respect the property and trims and one running Iceberg 1.10 that ignores it. So we have an even more fun problem where different clients are producing different normalizations. If we do it in constraints and make it part of the Spec itself we can say all V4 tables need to follow these directives. To be clear, constraints is a method of a providing requirements to writers like "Column X must not end in whitespace". An engine which cannot do this would not be allowed to commit but that requires a spec change to make sure everyone will be compliant. @aokolnychyi may have more info on this. I don't think we have any issue on doing documentation improvements if you like. -- 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]
