elkhand commented on issue #2033: URL: https://github.com/apache/iceberg/issues/2033#issuecomment-770067647
Verified with @RussellSpitzer (thanks!): You do not need to fix values of `flink.max-committed-checkpoint-id` in existing Iceberg metadata files either. You should be safe going forward: Flink/Presto/HMS/ Spark/Other engine should not be impacted by the wrong value (`Long.MAX_VALUE`) of `flink.max-committed-checkpoint-id` field. If you follow the above mentioned alternative flow, Flink will also **not** be impacted by the wrong value in Iceberg metadata files. > Snapshot Summary is used as a way to store engine/platform specific metadata which a user may need to know about and which some engines use for their own record keeping. > The Flink property above is only referenced to (written or read) by Flink’s IcbergFileComitter so there is no impact on any other system. > There should be no issue with this property having a wrong value for any system other than Flink. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
