You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Order of query axes should be COLUMNS, ROWS, PAGES, SECTIONS, CHAPTERS. This is consistent with SSASS 2005 and later.
The current order, as of olap4j 1.2, is COLUMNS, ROWS, PAGES, CHAPTERS, SECTIONS. This is based on Mondrian, which in turn was based upon an earlier version of MDX.
This is a breaking change, so we should implement in olap4j 2.0 but not olap4j 1.x. It is a fairly unusual problem, because few queries have more than 2 axes.
For maximum compatibility we recommend that people write ON AXIS(x) or ON x rather than ON CHAPTERS or ON SECTIONS.
Order of query axes should be COLUMNS, ROWS, PAGES, SECTIONS, CHAPTERS. This is consistent with SSASS 2005 and later.
The current order, as of olap4j 1.2, is COLUMNS, ROWS, PAGES, CHAPTERS, SECTIONS. This is based on Mondrian, which in turn was based upon an earlier version of MDX.
This is a breaking change, so we should implement in olap4j 2.0 but not olap4j 1.x. It is a fairly unusual problem, because few queries have more than 2 axes.
For maximum compatibility we recommend that people write
ON AXIS(x)
orON x
rather thanON CHAPTERS
orON SECTIONS
.See also rsim/mondrian-olap#35.
The text was updated successfully, but these errors were encountered: