[Mondrian] MDX issue : complex scenario for filtering

Jônatas Wingeter Rodrigues jonataswingeter at gmail.com
Wed Sep 22 17:44:28 EDT 2010

Hi Jeff

Thank you for the answer.

I have already tested the property to try to ignore invalid members, but it
didn't work for non existing object.

What exactly do you meant in separate dimensions for day? Today, *Day* is a
Level in the Hiearchy *Time*.

I wait your feedback and the others.



2010/9/22 <jeff.s.wright at thomsonreuters.com>

>  1) Look at property mondrian.rolap.ignoreInvalidMembersDuringQuery and
> see if that helps
> 2) Consider modeling time of day as a separate dim rather part of the time
> dimension
> --jeff
> *From:* mondrian-bounces at pentaho.org [mailto:mondrian-bounces at pentaho.org]
> *On Behalf Of *Jônatas Wingeter Rodrigues
> *Sent:* Wednesday, September 22, 2010 4:04 PM
> *To:* mondrian at pentaho.org
> *Subject:* [Mondrian] MDX issue : complex scenario for filtering
> Hi all,
> I'm new here and I'm starting with a complex scenario. Of course, I hope to
> help guys here instead to be just a listener.
> So,
> I have a cube in 3 dimensions: Network element, Time and KPI (Measure). We
> have been used MDX to make queries to this
> cube using a MDX parser API (which uses Olap4j under the table). This
> parser is a Fluent Interface responsible to facilitate
> the query generation through a concise and simple API.
> As well, I need to implement filtering, which includes: Filter by Element,
> Measure and Time.
> I've been blocked on Time issue. I can't understand completely the Time
> filtering in MDX.
> 1) : operator.
> When I try to run this query:
> WITH MEMBER [Time].[Filter] AS
> 'Aggregate({[Time].[2006]:[Time].[2010]})'
> The mondrian throws an exception of: object member not found (in this case,
> the 2006 object).
> I would like to know how to ignore this. I want to make filtering crossing
> many times and not necessary all the time objects
> shall be there. Ex: 2006 -> OK, 2007 -> Missing - 2008 -> OK, 2009 -> OK.
> If I make the filtering between 2006 and 2009,
> mondrian throws such error. What is the best way to avoid this? Try to
> disable member validation or change the query?
> 2) Parallel period:
> As I checked in documentation, the function parallel allows to gather
> member that are cousin among them.
> I would like to make a filter on a set of elements in my cube, just by
> selecting some hours of day (Ex: 2-3h AM, 5h-7h PM)
> crossing the entire Time members, which means: get the network elements
> whose have records in such hours, in all days, between a start and end date.
> The hierarchy of Time permits to get down from Year to Hour: Year, Month,
> Week, Day, Hour.
> These 2 things are my big problems. I have been facing these things during
> these last 2 weeks, and I didn't figure out a good solution.
> I have tried aggregate, PeriodsDate, YTD, unsuccessfully.
> I hope that some of you can help me on this challenger.
> Since know, I thank you only to be patient on this long reading.
> Regards,
> Jônatas
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20100922/b920624a/attachment.html 

More information about the Mondrian mailing list