Re: [I] check-ordering enablement for flink config [iceberg]

2024-12-01 Thread via GitHub
github-actions[bot] closed issue #10360: check-ordering enablement for flink config URL: https://github.com/apache/iceberg/issues/10360 -- 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

Re: [I] check-ordering enablement for flink config [iceberg]

2024-12-01 Thread via GitHub
github-actions[bot] commented on issue #10360: URL: https://github.com/apache/iceberg/issues/10360#issuecomment-2510325635 This issue has been closed because it has not received any activity in the last 14 days since being marked as 'stale' -- This is an automated message from the Apache

Re: [I] check-ordering enablement for flink config [iceberg]

2024-11-17 Thread via GitHub
github-actions[bot] commented on issue #10360: URL: https://github.com/apache/iceberg/issues/10360#issuecomment-2481696487 This issue has been automatically marked as stale because it has been open for 180 days with no activity. It will be closed in next 14 days if no further activity occur

Re: [I] check-ordering enablement for flink config [iceberg]

2024-05-21 Thread via GitHub
pvary commented on issue #10360: URL: https://github.com/apache/iceberg/issues/10360#issuecomment-2122772197 This is non-trivial, as currently the schema is compiled to the job graph. We need to decouple the schema either using external schema registry, or switching to less performant seria

Re: [I] check-ordering enablement for flink config [iceberg]

2024-05-20 Thread via GitHub
lei-xian0 commented on issue #10360: URL: https://github.com/apache/iceberg/issues/10360#issuecomment-2121768545 I see, so the flink sinks just doesn't support any schema change. Wondering is this something on the current road map and we can expect in the foreseeable future? -- This is

Re: [I] check-ordering enablement for flink config [iceberg]

2024-05-20 Thread via GitHub
pvary commented on issue #10360: URL: https://github.com/apache/iceberg/issues/10360#issuecomment-2121731857 You could create an operator to check for schema changes and fail the job if needed -- This is an automated message from the Apache Git Service. To respond to the message, please

Re: [I] check-ordering enablement for flink config [iceberg]

2024-05-20 Thread via GitHub
pvary commented on issue #10360: URL: https://github.com/apache/iceberg/issues/10360#issuecomment-2121152930 Currently Flink Sink is not able to handle the schema updates. You need to restart the job to handle schema changes. One hacky solution is to throw a `SuppressRestartsException` ex

[I] check-ordering enablement for flink config [iceberg]

2024-05-20 Thread via GitHub
lei-xian0 opened a new issue, #10360: URL: https://github.com/apache/iceberg/issues/10360 ### Feature Request / Improvement Hi team, can we get `check-ordering` config enabled for Flink writers as well? Currently the input is not tolerating schema order change compare with table sch