[MCOL-3588] cross engine join with DISTINCT returns null Created: 2019-11-04 Updated: 2020-08-25 Resolved: 2019-11-28 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | MariaDB Server |
| Affects Version/s: | None |
| Fix Version/s: | 1.2.6, 1.4.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Kyle Joiner (Inactive) | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Description |
|
When doing a distinct on a TEXT column while joining a Columnstore and InnoDB table returns the wrong result. The correct amount seems to be returned, but the TEXT column shows as NULL. If the tables are created of the same engine, the distinct works as expected. An example test case for the issue: MariaDB [test]> create table inno_table (text_column text, id varchar(8)); MariaDB [test]> create table cs_table (text_coumn text, id varchar(8), name varchar(10))engine=columnstore; MariaDB [test]> select distinct a.text_column, b.id, b.name from inno_table a join cs_table b on a.id=b.id;
------------
------------ As you can see, the distinct TEXT column show as null. If the tables are created in the same engine, either one, it works. MariaDB [test]> select distinct a.text_column, b.id, b.name from cs_table a join cs_inno_table b on a.id=b.id;
------------
------------ |
| Comments |
| Comment by Roman [ 2019-11-28 ] | |||||||||||||||||||||||||||||||||||
|
JFYI It is fixed in 1.4.1
| |||||||||||||||||||||||||||||||||||
| Comment by Roman [ 2019-11-28 ] | |||||||||||||||||||||||||||||||||||
|
It also works with unreleased 1.2.6 code:
|