Output columns not ordered correctly about saiku

[buggtb]

thats a limitation we cant do anything about for now
in the future we might be able to solve that (its olap4j related)

--paul

[alexis-via]

I am experiencing this bug (I think it's the same). My exact bug is "Saiku doesn't take into account the order of the measures". The bug happens when you have several measures in columns, but also in rows. When you try to re-order the measures inside the rows or inside the colums, the order in the result table stays the same.

Paul, you say that this bug is olap4j related. Does Jpivot also use olap4j ? Because this bug doesn't exist in Jpivot.

[buggtb]

Hi Guys,

The limitation was imposed by us in the Saiku code, because when you allow reordering in the olap4j query model it can on occasion create incorrect MDX and cause the wrong results.

We appreciate this isn't an ideal scenario and is something we are looking to address in the near future, but at the moment we value correct numbers of measure sorting i am afraid.

Tom

[pstoellberger]

will be fixed in 2.3 and the new query model

[haroldo-ok]

+1

[codenpk]

Why was this closed? Is it solved?