-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
'cannot use empty rangeList' error after upgrade from 359 to 362 #9424
Comments
i get the same "cannot use empty rangeList" error in 414 (on Amazon EMR) stack trace
it seems weird to me because Amazon Athena (V3 engine) is able to query this data just fine 🤷 |
@antonysouthworth-halter can you provide a sample file and query to reproduce the problem ? It's most likely a different problem from the original issue here. |
@antonysouthworth-halter File a new issue. Also check if disabling parquet column indexes helps you with |
Hi, I upgraded Trino from 359 to 362 and the error below showed up. (sensitive info masked)
Since this error hadn't been shown in 359, I believe it has something to do with the later updates, although I don't seem to be able to locate the culprit from the release notes.
I cannot supply the error-triggering parquet file, but if you guys want me to run some tests on it, I will be happy to help.
++ will dig deeper later when i have time, but there are multiple columns filled with all None values in this parquet, maybe it's the cause?
The text was updated successfully, but these errors were encountered: