-
Notifications
You must be signed in to change notification settings - Fork 908
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
Include encode type in the error message when unsupported Parquet encoding is detected #14453
Include encode type in the error message when unsupported Parquet encoding is detected #14453
Conversation
@ZelboK Could you run |
Will do, thanks for mentioning! |
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 for this. Just a few suggestions :)
/ok to test |
Question: I can't use
I hesitate doing 1, or 2, because I don't have enough context for the codebase to know the friction it may cause. I imagine there's some reason |
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.
Looking good, thanks for the quick changes :) A few more minor suggestions.
Co-authored-by: Ed Seidl <[email protected]>
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.
Sorry, a few more suggestions.
Co-authored-by: Ed Seidl <[email protected]>
Co-authored-by: Ed Seidl <[email protected]>
Co-authored-by: Ed Seidl <[email protected]>
Co-authored-by: Nghia Truong <[email protected]>
Is there any way I can test this behavior without having to rely on cudf python? Unfortunately I've run into a few blockers trying to get it set up. I'd like to finish this PR but it wouldn't be too efficient for me to offload the testing part to you like this. Builds are also quite slow without access to the cloud build artifacts. I should be able to create unsupported encodings in a unit test I hope? I wasn't sure if the tests didn't have them because they weren't perceived to add value or if there was some complication I'm unaware of. |
You could write a small C++ prog that calls |
Hm. Curious to know - when it comes to cuIO will I often need to run things from cudf python to test out functionality? If so that would justify me putting more effort into getting cudf python to work. I just have a lot more motivation for getting more experience with GPU programming than I do with tooling so I put it off lol. I'll spend a couple hours trying to figure this out (btw this is the problem i get when trying to run
Edit: NVM! I fixed them :D |
Might be misunderstanding, can you clarify a few things? Or are you saying that this logic
Edit: Okay so it would seem that this is the case.
is what I get, if I change |
I think @etseidl 's idea is to completely ignore UNSUPPORTED_ENCODING error in count_page_headers so we can get to print the unsupported encoding types after DecodePageHeaders, where it will be reported again. |
…n-msg' into feat-14209-exception-msg
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.
One more small request 😅
Then I think it's good to go.
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.
Thank you for the patch, looks good!
Few small suggestions
/ok to test |
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.
All my nits have been picked 😄. LGTM
/merge |
Description
Per #14209 this will list out unsupported encodings that were found.
Checklist