amogh-jahagirdar commented on code in PR #10711:
URL: https://github.com/apache/iceberg/pull/10711#discussion_r1681921169


##########
api/src/main/java/org/apache/iceberg/io/SupportsRecoveryOperations.java:
##########
@@ -0,0 +1,36 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.iceberg.io;
+
+/**
+ * This interface is intended as an extension for FileIO implementations to 
provide additional
+ * best-effort recovery operations that can be useful for repairing corrupted 
tables where there are
+ * reachable files missing from disk. (e.g. a live manifest points to data 
file entry which no
+ * longer exists on disk)
+ */
+public interface SupportsRecoveryOperations {
+
+  /**
+   * Perform a best-effort recovery of a file at a given path

Review Comment:
   How recovery is performed is left up to implementations but I think the one 
thing this interface is prescriptive on is that the expectation that it is 
*best effort*. It's not guaranteed that just because FileIO implementations 
implement the mixin that they will recover the file no matter what (e.g. 
there's a limit to versioning etc); as a result the interface doesn't surface 
an exception, rather just a boolean indicating success or not.
   
   I guess we may want to qualify what it means for a file to be recovered (it 
may be obvious but since it's an interface, it's better to be clear):
   
   It means that assuming no concurrent deletes of a file at that path, 
`fileIO.inputFile(path).exists()` must be true after this method call.
   
   If that definition makes sense to folks: I can update @RussellSpitzer 
@danielcweeks 



##########
api/src/main/java/org/apache/iceberg/io/SupportsRecoveryOperations.java:
##########
@@ -0,0 +1,36 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements.  See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership.  The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License.  You may obtain a copy of the License at
+ *
+ *   http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied.  See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.iceberg.io;
+
+/**
+ * This interface is intended as an extension for FileIO implementations to 
provide additional
+ * best-effort recovery operations that can be useful for repairing corrupted 
tables where there are
+ * reachable files missing from disk. (e.g. a live manifest points to data 
file entry which no
+ * longer exists on disk)
+ */
+public interface SupportsRecoveryOperations {
+
+  /**
+   * Perform a best-effort recovery of a file at a given path

Review Comment:
   Other thought I had:
   
   We could offer another method which uplevels the manifestFile and attempts 
to recover the manifest and if that's successful, attempt recovery of the data 
files. I discarded this case since someone could just traverse the metadata 
tree on their own and just use `recoverFile(String path)`. Also in that API, 
probably would need a response that's higher fidelity (the simplest is 
Map<String, Boolean>) than just a boolean since maybe a caller wants to take 
action if the manifest was recovered but data files weren't etc.



-- 
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: issues-unsubscr...@iceberg.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org

Reply via email to