-
Notifications
You must be signed in to change notification settings - Fork 290
Scan Delete Support Part 5: Positional Delete Parsing #1011
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
Conversation
52d3e2c
to
a14c3f2
Compare
e7f9102
to
efc45e5
Compare
643f47a
to
cfe6a91
Compare
5504434
to
decef64
Compare
343b034
to
7b755fd
Compare
7ea25cb
to
fc58a4f
Compare
4f8582f
to
18fb170
Compare
Hi, @sdd Would you mind to rebase this pr? |
…nal delete functionality
18fb170
to
ac36f29
Compare
@liurenjie1024 I've rebased this and it is ready to go. |
@liurenjie1024 / @Xuanwo please review when you get chance. The previous PRs are useless on their own without this small one and the small follow-up PR, #1017. |
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.
Thanks @sdd for this pr, LGTM! Just one minor nit.
Continues the series of scan delete file support PRs.
DeleteFileManager
crates/integration_tests/tests/shared_tests/read_positional_deletes.rs
to include a working end-to-end test that processes positional deletesIssue: #630