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 and reenable S3 Select for table with skip.header.line.count=1 #2349

Closed
findepi opened this issue Dec 26, 2019 · 4 comments
Closed

Fix and reenable S3 Select for table with skip.header.line.count=1 #2349

findepi opened this issue Dec 26, 2019 · 4 comments
Assignees

Comments

@findepi
Copy link
Member

findepi commented Dec 26, 2019

Hive table property skip.header.line.count seems to be ignored when S3 Select is enabled.

@findepi findepi added bug Something isn't working good first issue Good for newcomers correctness labels Dec 26, 2019
@findepi findepi self-assigned this Dec 30, 2019
@electrum electrum removed the good first issue Good for newcomers label Jan 4, 2020
@findepi
Copy link
Member Author

findepi commented Jan 11, 2020

S3 Select supports skipping first header line, but it was not working for me correctly in my testing.
We disable S3 Select for uncompressed files. when skip.header.line.count is set to non-zero.
cc @same3r

@findepi findepi changed the title Incorrect results when S3 Select is used on table with skip.header.line.count Fix and reenable S3 Select for table with skip.header.line.count=1 Jan 11, 2020
@same3r
Copy link
Contributor

same3r commented Mar 16, 2020

Hey, sorry for the delay in response. I have forwarded the issue to the concerned team to provide an ETA on the fix.

@findepi findepi removed bug Something isn't working correctness labels Mar 17, 2020
@findepi
Copy link
Member Author

findepi commented Mar 17, 2020

(I removed correctness and bug labels, because the bug is fixed from Presto perspective.)

@hashhar
Copy link
Member

hashhar commented Feb 22, 2024

S3 select is gone after #18241

@hashhar hashhar closed this as not planned Won't fix, can't repro, duplicate, stale Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants