[MCOL-1989] Querying view results in internal error: column is not found in info map Created: 2018-11-29  Updated: 2020-08-25  Resolved: 2019-06-18

Status: Closed
Project: MariaDB ColumnStore
Component/s: None
Affects Version/s: 1.1.6, 1.2.1
Fix Version/s: 1.1.0

Type: Bug Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Daniel Lee (Inactive)
Resolution: Fixed Votes: 1
Labels: None

Issue Links:
Relates
relates to MCOL-3388 Merge up 1.1 -> 1.2 Closed
Sprint: 2019-06

 Description   

If a user queries a specific view, they'll see the following error:

ERROR 1815 (HY000): Internal error: column is not found in info map.

However, the query in the view definition can be executed on its own with no issues.

 Comments   
Comment by Andrew Hutchings (Inactive) [ 2019-06-14 ]

The cause is the view name not being stored correctly for a derived table generated by the subquery. This meant that ColumnStore thought the column was outside of the view and generated the error. A fix is being tested now.

Comment by Andrew Hutchings (Inactive) [ 2019-06-14 ]

Pull request in engine and regression suite.

For QA: new test has been added in regression suite test001 called MCOL-1989. It is an anonymised simplified version of the user's test.

Comment by Daniel Lee (Inactive) [ 2019-06-18 ]

Build verified: 1.1.8-1 nightly

[root@localhost ~]# cat gitversionInfo.txt
server commit:
09faec8
engine commit:
0f5cc93

Reproduced the issue in 1.1.6-1. Verified the fix in 1.1.8-1 by execute the test case in the regressions suite.

.
.
.
MariaDB [mytest]>
MariaDB [mytest]> – Should return no result. Should not error.
MariaDB [mytest]> SELECT * from vv2;
Empty set (0.25 sec)
.
.
.

Generated at Thu Feb 08 02:32:52 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.