[MCOL-5237] MariaDB Columnstore: Views with null-replaced timestamps yield incorrect query results Created: 2022-09-29 Updated: 2024-01-12 |
|
| Status: | Confirmed |
| Project: | MariaDB ColumnStore |
| Component/s: | None |
| Affects Version/s: | 22.08.2, 6.4.2, 23.02.3 |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Major |
| Reporter: | andreas eschbacher | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Environment: |
MariaDB 10.6.9 CS 6.4.3 RHEL 8 |
||
| Attachments: |
|
| 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: 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. |