[MCOL-73] Wide table formatted display causes frontend to return error Created: 2016-05-23 Updated: 2017-06-05 Resolved: 2017-06-05 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | MariaDB Server |
| Affects Version/s: | None |
| Fix Version/s: | Icebox |
| Type: | Bug | Priority: | Minor |
| Reporter: | Dipti Joshi (Inactive) | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | relnote | ||
| Issue Links: |
|
||||||||
| Description |
|
During regression queries/misc/bug3281.sql shows following behavior SQL and the error reported
ERROR 1118 - is InnoDB or MyISAM error - It looks like when Select format(c1,2),.... - is creating a temporary table that is either Aria or InnoDB or MyISAM, instead of vtable(MariaDB ColumnStore own temporary table area) and hence giving this error from there As can be seen below if there is not format - but simply all the columns selected then the query goes through
Also if there is formatting but number of columns reduced then also query goes through
This implies that when the query result set are passed to MariaDB front end from MariaDB ColumnStore engine, there seems to be intermediate temporary table in InnoDB/Aria/MyISAM - which cannot handle the wide table and gives the error. David.Hall Please see the above analysis, let us know if "select format(c1,..) format(c2....)...." is causing intermediate temporary table on MariaDB Server frontend side to be created leading to this error. If this is true - this particular error is of lower priority right now - as it is on the display of the formatted result, rather then returning of the result and MariaDB ColumnStore's ability to store wide tables. |
| Comments |
| Comment by David Hall (Inactive) [ 2016-09-30 ] |
|
When vtable is on, which is most of the time, all select statements create an Aria temp table. That's part of the magic. We could try using MyISAM instead, as it will do just as well for this purpose. Don't know if it will help. |
| Comment by David Thompson (Inactive) [ 2017-06-05 ] |
|
Will track fix as part of |