LiorV10 opened a new issue, #15343: URL: https://github.com/apache/iceberg/issues/15343
### Query engine None ### Question I am trying to implement a custom full-refresh mechanism using a batch of messages flagged for 'full refresh' mode. These messages represent a complete dataset intended to replace all existing data in the target table. The process concludes with an 'EOD' (End of Data) message. Given that SMTs (Single Message Transforms) are stateless and cannot directly access or execute DDL/DML commands on the target database, how can I orchestrate the 'delete and replace' logic effectively? -- 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]
