pvary opened a new issue, #11536:
URL: https://github.com/apache/iceberg/issues/11536

   ### Proposed Change
   
   Flink Iceberg connector sink is the tool to write data to an Iceberg table 
from a continuous Flink stream. The current Sink implementations emphasize 
throughput over flexibility. The main limiting factor is that the Iceberg Flink 
Sink requires static table structure. The table, the schema, the partitioning 
specification need to be constant. If one of the previous things changes the 
Flink Job needs to be restarted. This allows using optimal record serialization 
and good performance, but real life use-cases need to work around this 
limitation when the underlying table has changed. We need to provide a tool to 
accommodate these changes.
   
   The following typical use cases are considered during this design:
   - Incoming Avro records schema changes (new columns are added, or other 
backward compatible changes happen). The Flink job is expected to update the 
table schema dynamically, and continue to ingest data with the new and the old 
schema without a job restart.
   - Incoming records define the target Iceberg table dynamically. The Flink 
job is expected to create the new table(s) and continue writing to them without 
a job restart.
   - The partitioning schema of the table changes. The Flink job is expected to 
update the specification and continue writing to the target table without a job 
restart.
   
   ### Proposal document
   
   
https://docs.google.com/document/d/1R3NZmi65S4lwnmNjH4gLCuXZbgvZV5GNrQKJ5NYdO9s
   
   ### Specifications
   
   - [ ] Table
   - [ ] View
   - [ ] REST
   - [ ] Puffin
   - [ ] Encryption
   - [X] Other


-- 
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]

Reply via email to