danielcweeks commented on code in PR #14509: URL: https://github.com/apache/iceberg/pull/14509#discussion_r2499909507
########## api/src/main/java/org/apache/iceberg/SnapshotUpdateValidator.java: ########## @@ -0,0 +1,46 @@ +/* + * 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; + +import java.util.function.BiConsumer; + +/** + * Interface to support validating snapshots during the commit process. + * + * <p>Validation will be called after the table metadata is refreshed but before the updates are + * committed to the table. + */ +@FunctionalInterface +public interface SnapshotUpdateValidator + extends BiConsumer<Iterable<Snapshot>, Iterable<Snapshot>> { Review Comment: I was thinking of this in context of the refresh introducing external changes to the localized commit process that render the operations invalid, but I guess it's probably unlikely that you could (or should) rely on the same external factor to get back into a valid state. (I can think of a few cases you could do this, but none of them are something I would recommend someone to do). If there's only one option then (`ValidationException`), then it doesn't matter to me whether we require throw or return a boolean. -- 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]
