[Mondrian] Deprecating Member Ordinal

Nicholas Goodman ngoodman at bayontechnologies.com
Mon Jan 14 19:49:47 EST 2013


On Jan 14, 2013, at 2:14 PM, Luc Boudreau wrote:

> 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.
> 

I don't see it HAS to be an INTEGER.  I do see there should be some value to order them globally (hash, etc) that sorts properly (more below).

Will the new ORDER KEY be available as a member property, and sort properly across the dimension?

I understand that Mondrian, if asked (via .Members) will return them in that order, but if they're OUT of that order (MDX magic), how do we get them back in natural order?

I know I'm talking about raw MDX here and that's of lesser concern than what Analyzer generates, but it's not uncommon to do some "fancy" set stuff, and then need the data back in the "natural" sort order.  Take for an example, how to filter to the top 6 quarters in the past 5 years, but for dashboard display them in chronological "natural" order (composite keys of years/quarters).

We can now do something like (pseudo-code):
with 
set Qtrs as 'Time.Quarters.Members'
set Top6 Head(Order ( [Qtrs], Measures.Sales ), 6)
set ReadyForDisplay Order ([Top6], Time.CurrentMember.Properties("MEMBER_ORDINAL") )
<< normal MDX for display >>

Will 4.0 retain the same ability in MDX to get back into natural order?

Nick
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20130114/6d6eb20c/attachment.html 


More information about the Mondrian mailing list