Skip to content

GH-47053: [C++] Stricter data validation on Run-end encoded #47174

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

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

raulcd
Copy link
Member

@raulcd raulcd commented Jul 23, 2025

TBD

Still under clarification on the issue

Rationale for this change

Stricter validation on Run-end encoded could help identify some programming errors as the one found on #47029

What changes are included in this PR?

When doing REE validation ensure equality between run_ends_data->length and values_data->length

Are these changes tested?

Yes

Are there any user-facing changes?

No

This comment was marked as outdated.

@raulcd raulcd changed the title [C++] Stricter data validation on Run-end encoded GH-47053: [C++] Stricter data validation on Run-end encoded Jul 23, 2025
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.

1 participant