You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
Version
2.0.0
What's Wrong?
When querying a table with time partitions, using time format like 'YYYY-mm-dd hh:mm:ss' would scan the correct partitions in query plan, but using format like 'YYYY/mm/dd hh:mm:ss' or 'YYYY-mm-ddThh:mm:ss' would perform a whole table scan but still yield the correct results.
What You Expected?
The query plan should scan the correct partition based on the filter regardless of the format.
explain select * from test_table
where __time between convert_tz('2024-03-01 00:00:00', '+08:00', 'America/Los_Angeles') and convert_tz('2024-03-01 00:00:00', '+08:00', 'America/Los_Angeles');
explain select * from test_table
where __time between CAST('2024-03-01T00:00:00' as datetime) and CAST('2024-03-30T23:59:59' as datetime);
Search before asking
Version
2.0.0
What's Wrong?
When querying a table with time partitions, using time format like 'YYYY-mm-dd hh:mm:ss' would scan the correct partitions in query plan, but using format like 'YYYY/mm/dd hh:mm:ss' or 'YYYY-mm-ddThh:mm:ss' would perform a whole table scan but still yield the correct results.
What You Expected?
The query plan should scan the correct partition based on the filter regardless of the format.
How to Reproduce?
Anything Else?
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: