aiborodin commented on code in PR #14810:
URL: https://github.com/apache/iceberg/pull/14810#discussion_r2618007875


##########
flink/v2.0/flink/src/main/java/org/apache/iceberg/flink/sink/dynamic/DynamicCommitter.java:
##########
@@ -126,9 +125,14 @@ public void 
commit(Collection<CommitRequest<DynamicCommittable>> commitRequests)
       return;
     }
 
-    // For every table and every checkpoint, we store the list of 
to-be-committed
-    // DynamicCommittable.
-    // There may be DynamicCommittable from previous checkpoints which have 
not been committed yet.
+    /*
+      Each (table, branch, checkpoint) triplet must have only one commit 
request.
+      There may be commit requests from previous checkpoints which have not 
been committed yet.
+
+      We currently keep a List of commit requests per checkpoint instead of a 
single CommitRequest<DynamicCommittable>
+      to process the Flink state from previous releases, which had multiple 
commit requests due to a bug in the upstream
+      DynamicWriteResultAggregator. We should replace this with a single 
commit request in the next major release.

Review Comment:
   @pvary We can keep lists of committables for a longer period. Removing them 
from DynamicCommitter is a separate step, independent from this change. The 
current change is fully backward compatible.
   
   Although I'd prefer to remove lists of committables early, in the next minor 
release, 1.11, because it creates unnecessary complications and pollutes the 
code, making it harder to reason about.
   Additionally, we will still provide users with a smooth migration path. 
Users can upgrade to patch version 1.10.1 to resolve their current state and 
then upgrade to the latest minor version: 1.11+. We can always detect multiple 
committables in the `DynamicCommitter` state and ask users to upgrade to the 
previous patch version first.



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