<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6001.18023" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><FONT face=Verdana
color=#000080 size=2>General principles:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><FONT face=Verdana
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><FONT face=Verdana
color=#000080 size=2>1. Default behavior should be the same as
SSAS.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><FONT face=Verdana
color=#000080 size=2>2. Behavior should be the same for native and in-memory non
empty.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><FONT face=Verdana
color=#000080 size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><SPAN
class=549030007-11042008><FONT face=Verdana color=#000080 size=2>If you don't
like the default behavior, you can add a property, disabled by default of
course.</FONT></SPAN></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><SPAN
class=549030007-11042008><FONT face=Verdana color=#000080
size=2></FONT></SPAN></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><SPAN
class=549030007-11042008><FONT face=Verdana color=#000080 size=2>I would view
differences between 'native non empty' and 'in-memory non empty' behavior
as serious bugs. It's extremely confusing for an end-user to get different
results, and it makes it more difficult to support the product, since people
don't generally post their settings when they have a
bug.</FONT></SPAN></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><SPAN
class=549030007-11042008><FONT face=Verdana color=#000080
size=2></FONT></SPAN></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><SPAN
class=549030007-11042008><FONT face=Verdana color=#000080 size=2>Based on these
principles, what action should we take? Sounds like option #1, except that the
bug would be high priority. Correct me if I'm wrong.</FONT></SPAN></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><SPAN
class=549030007-11042008><FONT face=Verdana color=#000080
size=2></FONT></SPAN></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=549030007-11042008><SPAN
class=549030007-11042008><FONT face=Verdana color=#000080
size=2>Julian</FONT></SPAN></SPAN></DIV><FONT face=Verdana color=#000080
size=2></FONT><FONT face=Verdana color=#000080 size=2></FONT><BR>
<BLOCKQUOTE
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000080 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> mondrian-bounces@pentaho.org
[mailto:mondrian-bounces@pentaho.org] <B>On Behalf Of </B>Ajit Vasudeo
Joglekar<BR><B>Sent:</B> Thursday, April 10, 2008 3:13 AM<BR><B>To:</B>
Mondrian developer mailing list<BR><B>Subject:</B> Re: [Mondrian] Native vs.
Regular Non Empty <Level>.MEMBERS Issue<BR></FONT><BR></DIV>
<DIV></DIV><FONT face=Verdana color=#000080 size=2></FONT><FONT face=Verdana
color=#000080 size=2></FONT><FONT face=Verdana color=#000080
size=2></FONT><FONT face=Verdana color=#000080 size=2></FONT><BR><FONT
face=sans-serif size=2>I propose the following</FONT> <BR><BR><FONT
face=sans-serif size=2>We roll back the changes done in change list #10641.
After doing this, bug: </FONT><FONT size=3>1722959 will reopen and can be
marked as </FONT><FONT face=sans-serif size=2>a non issue and bug:
</FONT><FONT size=3>1909516 will</FONT><FONT face=sans-serif size=2> get
fixed. As far as 1909516 is concerned it is possible to add check around
IgnoreUnrelatedDimension and get it working. But this makes ValidMeasure
dependent on IgnoreUnrelatedDimension which is not a good idea. Hence the only
way out is to roll back change #10641</FONT> <BR><BR><FONT face=sans-serif
size=2>As far as the difference in behavior between native non empty and in
memory non empty (motivation behind bug 1722959) regarding the handling of
empty rows/ columns with literal "1" calc members is concerned we have couple
of options:</FONT> <BR><FONT face=sans-serif size=2>1) can log a new low
priority bug fixing of this will involve changing native non empty behavior to
not to eliminate the above said rows/columns. Opposite of bug 1722959</FONT>
<BR><FONT face=sans-serif size=2>2) document it and live with the difference
in behavior. whoever doesn't want this native non empty behavior may turn of
the the feature using property </FONT><BR><BR><FONT face=sans-serif
size=2>Requesting comments</FONT> <BR><BR><FONT face=sans-serif
size=2>Thanks</FONT> <BR><BR><FONT face=sans-serif
size=2>-Ajit</FONT></BLOCKQUOTE></BODY></HTML>