[Mondrian] Mondrian vs Olap4j vs Ole DB for OLAP Named Axes definitions
julianhyde at gmail.com
Mon Mar 28 21:05:55 EDT 2016
I have logged https://github.com/olap4j/olap4j/issues/41 <https://github.com/olap4j/olap4j/issues/41> and intend to fix in olap4j 2.0. I guess Mondrian 4 will inherit that fix, and Mondrian 3.x will not. In any case, Roland’s workaround of using ‘ON 4’ or ‘ON 5’ rather than ‘ON SECTIONS’ is recommended.
> On Mar 28, 2016, at 4:58 PM, Manuel Aristarán <manuel at jazzido.com> wrote:
>> On Mar 28, 2016, at 7:38 PM, Julian Hyde <julianhyde at gmail.com <mailto:julianhyde at gmail.com>> wrote:
>> […] I suspect that Microsoft have quietly changed the order since the first MDX specification. That would explain why Oracle/Essbase and IBM have made the same mistake that Mondrian and olap4j have.
> FWIW, mondrian-olap  was also bit by that bug: https://github.com/rsim/mondrian-olap/pull/35 <https://github.com/rsim/mondrian-olap/pull/35>
>  https://github.com/rsim/mondrian-olap <https://github.com/rsim/mondrian-olap>
> Manuel Aristarán <manuel at jazzido.com <mailto:manuel at jazzido.com>>
> http://jazzido.com <http://jazzido.com/>
> Mondrian mailing list
> Mondrian at pentaho.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mondrian