mxm commented on PR #11497:
URL: https://github.com/apache/iceberg/pull/11497#issuecomment-2520575831

   Concerning your questions in 
https://github.com/apache/iceberg/pull/11497#issuecomment-2519720233, my 
preferences are the same as yours:
   
   - **State handling and restoration**: I prefer a simpler, stateless design 
in favor of optimizing for failure cases.
   - **Table schema, specification, and configuration changes**: We're planning 
to run the table maintenance continuously, so querying only once at Flink job 
deployment would eventually yield outdated table information. If it doesn't add 
too much complexity querying the table at planning time and sending the results 
through the wire is my preference. This will also ensure that all executors 
share the same state.
   - **Error handling**: Using side outputs is the more programmatic approach 
to error handling. Propagating the full error seems preferable. I think we can 
stringify the stacktrace to avoid Exception class changes.


-- 
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: issues-unsubscr...@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to