Skip to content
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

Spark: Read DVs when reading from .position_deletes table #11657

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

nastra
Copy link
Contributor

@nastra nastra commented Nov 26, 2024

this is part of #11122 and has been extracted from #11545

@nastra nastra force-pushed the dv-iterable-for-position-deletes branch 2 times, most recently from b347427 to cd35ea5 Compare November 27, 2024 13:29
@nastra nastra force-pushed the dv-iterable-for-position-deletes branch 2 times, most recently from 2ab2cda to b79a7da Compare November 27, 2024 14:07
@nastra nastra force-pushed the dv-iterable-for-position-deletes branch from b79a7da to 2512b5f Compare November 27, 2024 15:18

@Override
public CloseableIterator<InternalRow> iterator() {
PuffinReader reader = builder.build();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[optional] might be too much, but can we have one reader per DV file ? considering specifically for this use case we will have to read all the blobs in the DV file eventually.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you have a particular use case in mind as this isn't something that is being needed currently when reading the PositionDeletesTable?

@nastra nastra force-pushed the dv-iterable-for-position-deletes branch from 9a47998 to 3e1bafe Compare November 29, 2024 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants