-
Notifications
You must be signed in to change notification settings - Fork 275
feat: validate snapshot write compatibility #1772
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
kaushiksrini
wants to merge
9
commits into
apache:main
Choose a base branch
from
kaushiksrini:check-write-compatibility-append
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+119
−1
Open
Changes from 1 commit
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
949e140
feat: validate snapshot write compatibility
kaushiksrini e631ddf
reuse ancestors_of existing functionality
kaushiksrini 740db96
Update pyiceberg/table/update/snapshot.py
kaushiksrini 611b017
fix mypy errors
kaushiksrini 0923dc4
add tests for verifying snapshot compatibility
kaushiksrini 57e0f90
update parent snapshot when there are conflicts and change exception
kaushiksrini 5122039
Merge branch 'main' into check-write-compatibility-append
Fokko 66849dd
add table content verification for tests
kaushiksrini 0824c35
modify allowed operations for replace
kaushiksrini File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,53 @@ | ||
# 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. | ||
|
||
from typing import Callable, Iterable, Iterator, Optional | ||
from pyiceberg.table.snapshots import Snapshot | ||
|
||
|
||
def ancestors_of(snapshot_id: Optional[int], lookup_fn: Callable[[int], Optional[Snapshot]]) -> Iterable[Snapshot]: | ||
Fokko marked this conversation as resolved.
Show resolved
Hide resolved
|
||
def _snapshot_iterator(snapshot: Snapshot) -> Iterator[Snapshot]: | ||
next_snapshot: Optional[Snapshot] = snapshot | ||
consumed = False | ||
|
||
while next_snapshot is not None: | ||
if not consumed: | ||
yield next_snapshot | ||
consumed = True | ||
|
||
parent_id = next_snapshot.parent_snapshot_id | ||
if parent_id is None: | ||
break | ||
|
||
next_snapshot = lookup_fn(parent_id) | ||
consumed = False | ||
|
||
snapshot: Optional[Snapshot] = lookup_fn(snapshot_id) | ||
if snapshot is not None: | ||
return _snapshot_iterator(snapshot) | ||
else: | ||
return iter([]) | ||
|
||
def ancestors_between(starting_snapshot_id: Optional[int], current_snapshot_id: Optional[int], lookup_fn: Callable[[int], Optional[Snapshot]]) -> Iterable[Snapshot]: | ||
if starting_snapshot_id == current_snapshot_id: | ||
return iter([]) | ||
|
||
return ancestors_of( | ||
current_snapshot_id, | ||
lambda snapshot_id: lookup_fn(snapshot_id) if snapshot_id != starting_snapshot_id else None | ||
) | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the spec may need a re-review because I think it's inaccurate to say that we only need to verify that the files we are trying to delete are still available when we are executing a
REPLACE
orDELETE
operation.In Spark, we also validate whether there's been a conflicting appends when we use
SERIALIZABLE
isolation level:https://github.com/apache/iceberg/blob/9fc49e187069c7ec2493ac0abf20f73175b3df89/spark/v3.5/spark/src/main/java/org/apache/iceberg/spark/source/SparkWrite.java#L368-L374
I think it would be helpful to introduce all three types of isolation levels
NONE
,SERIALIZABLE
andSNAPSHOT
, and verify if conflicting appends or deletes have been introduced in the underlying partitions to be aligned with the implementation in SparkThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @sungwy for jumping in here, and creating the issues 🙌
Indeed, depending on whether we do snapshot or serializable isolation, we should allow for new data (or not). Would you be willing to split out the different levels in a separate PR? It would be nice to get this in so we can start working independently on the subtasks that you created.
I think this one was mostly blocked on #1903