-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 LZO decompression #10123
Fix LZO decompression #10123
Conversation
✅ Deploy Preview for meta-velox canceled.
|
@Yuhta Can you take a look? Thanks! |
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.
@majetideepak Thanks for fixing this! The bug also indicates insufficient tests to cover different compression schemes in existing E2EFilterTest. #8103. We will need to make the tests to loop over different compression schemes in future PRs.
@yingsu00 We don't currently have support for lzo compression. We should add that support as well. |
@pedroerp can you please help review this? Thanks. |
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!
We should at some point have an actual fuzzer suite to cross test all sorts of file formats and compression schemes.
TEST_F(ParquetReaderTest, testLzoDataPage) { | ||
const std::string sample(getExampleFilePath("lzo.parquet")); | ||
|
||
facebook::velox::dwio::common::ReaderOptions readerOptions{leafPool_.get()}; |
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.
nit: we should add tests to a "facebook::velox::dwio::test" sort of namespace, so you could just do "common::ReaderOptions" here
@pedroerp has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
resolves #9618
The output is verified via Presto.