[MCOL-252] ‘ONLY_FULL_GROUP_BY’ is not present. Created: 2016-07-12 Updated: 2022-11-05 Resolved: 2022-11-05 |
|
| Status: | Closed |
| Project: | MariaDB ColumnStore |
| Component/s: | ExeMgr |
| Affects Version/s: | 1.0.1 |
| Fix Version/s: | Icebox |
| Type: | New Feature | Priority: | Minor |
| Reporter: | David Hill (Inactive) | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 4 |
| Labels: | None | ||
| Epic Link: | ColumnStore Compatibility Improvements |
| Description |
|
reported by an alpha customer in google groups: I plan to use the Columnstore as a DB backend to Pentaho, an open source Business Intelligence platform. The current Alpha release is working smoothly for a lot of things, the performance is great, I am happy with it. But, in some cases the BI solution (the Mondrian part, to be more precise) generates a query that not fully compliant with the SQL-92 regarding the use of group by. Normally, MariaDB would accept these queries in case the ‘ONLY_FULL_GROUP_BY’ mode is not set, so it is not present in the ‘sql_mode’ variable. When I check the ‘sql_mode’ on this alpha release, I get this: 'IGNORE_SPACE,STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION' So, the ‘ONLY_FULL_GROUP_BY’ is not present. Despite of this the DB server does not accept a query like this: select year, month, service_group, count I get an error: SQL Error [1815] [HY000]: Internal error: IDB-2021: bi.income.year is not in GROUP BY clause. All non-aggregate columns in the SELECT and ORDER BY clause must be included in the GROUP BY clause. Any idea, suggestion regarding how can I set the Columnstore up to accept such type of queries? I am pretty sure that many others will be affected by this behavior. More or less everybody who plans to use it as an OLAP DB backend. |
| Comments |
| Comment by Dev OneOone [ 2018-11-13 ] |
|
I'm affected by this too. |
| Comment by Todd Stoffel (Inactive) [ 2022-11-05 ] |
|
This item is being closed because it was well passed the expiration date with no activity. If you suspect this was done in error please create a new ticket. |