[Mondrian] Deprecating Member Ordinal
lucboudreau at gmail.com
Mon Jan 14 17:14:06 EST 2013
This won't affect the results of mdx queries, nor the ordering of members
returned from meta data calls. We were assigning an ordinal to members
after ordering them, and this is what we are trying to eliminate.
Using the order key will also allow us to represent complex composite keys.
On Jan 14, 2013 4:59 PM, "Pedro Alves" <pmgalves at gmail.com> wrote:
> Will this affect the Order function to find the position in which a member
> appears in a set?
> On Monday, January 14, 2013, Kurtis Walker wrote:
>> Mondrian Users,
>> We are planning to deprecate the Member Ordinal property in Mondrian 4
>> and have it always return a value of "0". It would also be removed from
>> the OLAP4J spec. This propery has been deprecated in the XMLA spec and
>> will always return "0" in Microsoft Analysis Services. We'd like to find
>> out if any Mondrian clients are using Member Ordinal.
>> In addition, we are considering adding a new OLAP4J property called
>> Order Key. Order Key would be the value or set of values that should be
>> using for ordering members.
>> Let us know if you have any thoughts on these issues. Thanks!
>> Mondrian mailing list
>> Mondrian at pentaho.org
> Mondrian mailing list
> Mondrian at pentaho.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mondrian