[Mondrian] Mondrian change 13915: XMLA queries now return information about the filter axis, even if it is empty

Julian Hyde jhyde at pentaho.com
Wed Nov 17 15:38:42 EST 2010


Matt,
 
Can you please review change 13915.
 <http://p4web.eigenbase.org/@md=d&c=6PU@/13915?ac=10>
http://p4web.eigenbase.org/@md=d&c=6PU@/13915?ac=10

I know that your team added the DataOmitDefaultSlicer flag to prevent dozens
of unused dimensions coming back in the slicer each request. When was no
WHERE clause, or the WHERE clause evaluated to an empty set, there would be
no members in the slicer, and therefore no slicer axis would be returned.
This is a problem for the olap4j driver, since it needs to distinguish
between a missing WHERE clause (one tuple with zero members) and a WHERE
clause that evaluates to empty (zero tuples).
 
So, I have changed the mondrian XMLA server's response. It always returns a
slicer axis. In the cases above, the slicer will either have no tuples or
one tuple with no positions, so the change adds only a few bytes to each
XMLA response.
 
Sergey,
 
I know you are interested in running Mondrian with Excel 2007. You might
also wish to review this change.
 
Julian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20101117/e2d5b09b/attachment.html 


More information about the Mondrian mailing list