Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
22.08.2, 6.4.2, 23.02.3
-
None
-
None
-
MariaDB 10.6.9 CS 6.4.3 RHEL 8
-
2024-1
Description
We plan to store null in the timestamps, and use a Pentaho-specific view to null-replace them.
When trying this out, we found (again) a discrepancy between InnoDB and Columnstore:
what should work (and does in InnoDB) yields incorrect query results in Columnstore.
In detail: using YEAR(...) = 1970 in a WHERE condition on a null-replaced date yields no rows in case of Columstore-tables-based view, but the correct result set when the view is based on a InnoDB table.
See the attached SQL.
Attachments
Issue Links
- is blocked by
-
MCOL-5759 Wrong filter ordering for query with sub select
- Closed