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

Fix unknown column name error when filtering ORC file with no names #2007

Merged
merged 2 commits into from
Mar 24, 2021

Conversation

jlowe
Copy link
Member

@jlowe jlowe commented Mar 24, 2021

rapidsai/cudf#7624 recently exposed an issue in the plugin when handling an ORC file with no column names. The plugin was filtering the stripes based on the columns being referenced but then asking for all columns in the original file schema. After the recent cudf change, that caused an "Unknown column" exception to be thrown.

This updates the code to filter the requested columns to the referenced columns when dealing with a file that has no column names. The existing no-column-name ORC test now passes with this change, so no new test was added.

Signed-off-by: Jason Lowe <jlowe@nvidia.com>
@jlowe jlowe added this to the Mar 15 - March 26 milestone Mar 24, 2021
@jlowe jlowe self-assigned this Mar 24, 2021
@jlowe
Copy link
Member Author

jlowe commented Mar 24, 2021

This will need to be upmerged with #2005 before the CI build will pass.

@jlowe
Copy link
Member Author

jlowe commented Mar 24, 2021

build

@sameerz sameerz added the bug Something isn't working label Mar 24, 2021
@jlowe jlowe merged commit ec2dcd7 into NVIDIA:branch-0.5 Mar 24, 2021
nartal1 pushed a commit to nartal1/spark-rapids that referenced this pull request Jun 9, 2021
nartal1 pushed a commit to nartal1/spark-rapids that referenced this pull request Jun 9, 2021
@jlowe jlowe deleted the fix-orc-no-names branch September 10, 2021 15:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants