flyrain commented on a change in pull request #2564:
URL: https://github.com/apache/iceberg/pull/2564#discussion_r629765099



##########
File path: core/src/main/java/org/apache/iceberg/MetadataLocationUtils.java
##########
@@ -58,17 +53,22 @@ private static void miscMetadataFiles(String 
metadataFileLocation, Set<String> m
     if (metadataFileLocation == null) {
       return;
     }
-    try {
-      TableMetadata metadata = TableMetadataParser.read(io, 
metadataFileLocation);
-      List<TableMetadata.MetadataLogEntry> metadataLogEntries = 
metadata.previousFiles();
-      List<String> previousMetadataFiles =
-          
metadataLogEntries.stream().map(TableMetadata.MetadataLogEntry::file).collect(Collectors.toList());
+    TableMetadata metadata = TableMetadataParser.read(io, 
metadataFileLocation);
+    List<TableMetadata.MetadataLogEntry> metadataLogEntries = 
metadata.previousFiles();
+    List<String> previousMetadataFiles =
+        metadataLogEntries.stream().map(TableMetadata.MetadataLogEntry::file)
+            .collect(Collectors.toList());
+    if (previousMetadataFiles.size() > 0) {
       metaFiles.addAll(previousMetadataFiles);
-      if (isRecursive && previousMetadataFiles.size() > 0) {
-        miscMetadataFiles(previousMetadataFiles.get(0), metaFiles, io, 
isRecursive);
+      if (isRecursive) {

Review comment:
       1. In that sense, can we remove method getOtherMetadataFilePaths and 
getManifestListPaths in BaseAction?
   2. Not sure I understand, does removal of orphan files need all reachable 
metadata json files? Base on comment from #2415, maybe we could hold on the 
implementation recursive part?




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

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