raunaqmorarka commented on code in PR #18076:
URL: https://github.com/apache/iceberg/pull/18076#discussion_r4011793961


##########
core/src/main/java/org/apache/iceberg/ManifestMergeManager.java:
##########
@@ -193,34 +200,54 @@ private ManifestFile createManifest(int specId, 
List<ManifestFile> bin) {
     }
 
     ManifestWriter<F> writer = newManifestWriter(spec(specId));
+    ExecutorService workerPool = workerPoolSupplier.get();
+    Deque<FutureTask<List<ManifestEntry<F>>>> pendingReads = new 
ArrayDeque<>();
     boolean threw = true;
     try {
-      for (ManifestFile manifest : bin) {
-        boolean isCommitted =
-            manifest.snapshotId() != null && snapshotId() != 
manifest.snapshotId();
-        try (ManifestReader<F> reader = newManifestReader(manifest, 
isCommitted)) {
-          for (ManifestEntry<F> entry : reader.entries()) {
-            if (entry.status() == Status.DELETED) {
-              // suppress deletes from previous snapshots. only files deleted 
by this snapshot
-              // should be added to the new manifest
-              if (entry.snapshotId() == snapshotId()) {
-                writer.delete(entry);
-              }
-            } else if (entry.status() == Status.ADDED && entry.snapshotId() == 
snapshotId()) {
-              // adds from this snapshot are still adds, otherwise they should 
be existing
-              writer.add(entry);
-            } else {
-              // add all files from the old manifest as existing files
-              writer.existing(entry);
-            }
+      // reads run on the worker pool ahead of the writer, which consumes them 
in bin order. a

Review Comment:
   Switched the bound from entry count to manifest bytes. That drops the 
streaming path and the entry-count handling, and it tracks stats width, since a 
manifest with wide stats holds fewer entries per byte. One read is always in 
flight, and further reads are submitted while the pending manifests stay under 
8MB.
   



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