richiebachala commented on issue #1015: URL: https://github.com/apache/iceberg-go/issues/1015#issuecomment-5976285736
I'm interested in helping resolve this Java/PyIceberg parity question after my first iceberg-go issue is complete. I agree this is a defaults-policy decision rather than just a constant change: the compatibility and contention-latency effects deserve an explicit maintainer decision, tests, and a release note if the default changes. Would comparative tests/benchmarks under conflicts be useful to inform that decision? I'm not starting a parallel PR or treating this discussion as claimed implementation work. -- 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]
