-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Query failing with valid partition filter in v448 but succeeds in v437 #22268
Comments
cc: @marcinsbd |
@abhinavdangi can you share the query plans for success (version 437) and failure ( version 447 or 448). |
Version 448
|
Version 437
|
@abhinavdangi Can you provide the type of the column test_partition_table_1.part_col? |
Had mentioned the table definitions above.
|
I did a test when partition column part_col is of the type integer instead of varchar as in example above so the cast is integer->bigint and it works.
It seems to me that issue could be connected with way how we handle different casts. |
@marcinsbd, your analysis seems correct. We're going to have to look into how to perform speculative pushdown of expressions that may fail. I have some very rough ideas on how to go about this. I'll post later. |
Trino 448 is set up with the following property.
delta.query-partition-filter-required=true
While querying a table with partitions, with cast condition on the partition column;
It fails with error:
Whereas, considering the plain condition without casting, it succeeds.
Table definitions are as follows:
This is failing with versions 447 and 448 but succeeding with 437.
Please help.
The text was updated successfully, but these errors were encountered: