The patch breaks dict columns filtering, e.g.
{format}select count
from lineitem where l_comment > l_shipinstruct;{format}
[MCOL-4791] Fix ColumnCommand fudged data type format to clearly identify CHAR vs VARCHAR Created: 2021-07-02 Updated: 2023-07-01 |
|
| Status: | Stalled |
| Project: | MariaDB ColumnStore |
| Component/s: | ExeMgr, PrimProc |
| Affects Version/s: | 6.1.1 |
| Fix Version/s: | 23.10 |
| Type: | Task | Priority: | Major |
| Reporter: | Alexander Barkov | Assignee: | Roman |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||||||||||
| Description |
|
Under terms of
This will remove a lot of strnlen() calls used e.g. in the row aggregation code. In order to do the format change easier we need to clearly distinguish CHAR vs VARCHAR on the PrimProc side. Currently it's not possible to distinguish because ExeProc sends the data type in ColumnCommand in a "fudged" format as follows:
The current notation uses VARCHAR(8) to mean "a CHAR or VARCHAR dictionary column", no matter what the original data type is (CHAR or VARCHAR). Under terms of this task we'll change the code as follows:
The new fudged data type mapping will look as follows:
|
| Comments |
| Comment by Roman [ 2021-07-13 ] |
|
The patch breaks dict columns filtering, e.g. {format}select count from lineitem where l_comment > l_shipinstruct;{format}
|