[Mondrian] adding warning support to Mondrian's Connection/Query API

[John V. Sichi]

I haven't added the warning support yet, but I did implement the missing 
members feature below (eigenchange 9198).  When enabled, it will 
silently (for now) convert invalid members into the null member.

JVS

>> -----Original Message-----
>> From: mondrian-bounces at pentaho.org 
>> [mailto:mondrian-bounces at pentaho.org] On Behalf Of John V. Sichi
>> Sent: Wednesday, April 04, 2007 1:08 PM
>> To: mondrian at pentaho.org
>> Subject: [Mondrian] adding warning support to Mondrian's 
>> Connection/Query API
>>
>> Here's a use-case.  We would like to add a property 
>> mondrian.rolap.ignoreInvalidMembersDuringQuery (similar to 
>> the existing 
>> mondrian.rolap.ignoreInvalidMembers, which only affects schema 
>> validation).  When this property is enabled, missing members would be 
>> replaced with the null member (same rule Zelaine added for schema 
>> validation).  This allows a saved report to be resilient to data 
>> changes, even if it refers to members explicitly.  MSAS 2005 
>> introduced 
>> a "missing member" mode for this:
>>
>> http://sqljunkies.com/WebLog/mosha/archive/2005/06/09/mdx_miss
>> ing_members_mode.aspx
>>
>> However, we may want to let the user know that there's a 
>> mismatch with 
>> what was requested at the time the report was saved.  Posting 
>> a warning 
>> at the point where we detect the invalid member would be easy if the 
>> infrastructure were there.
>>
>> JVS
>> _______________________________________________
>> Mondrian mailing list
>> Mondrian at pentaho.org
>> http://lists.pentaho.org/mailman/listinfo/mondrian
>>
> 
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org
> http://lists.pentaho.org/mailman/listinfo/mondrian
>