<div dir="ltr">Thanks for the reply<div><br></div><div>- xmlns prefixes</div><div>The namespaces are still declared, inner elements just don't get prefixed.</div><div>Could still use the olap4j xmla driver with this version.</div>
<div><br></div><div>- <span style="font-family:arial,sans-serif;font-size:13px">Full hierarchy names</span></div><div><span style="font-family:arial,sans-serif;font-size:13px">Looks like in SSAS the inclusion of dimension name can be defined by dimension (</span><font face="arial, sans-serif"><a href="http://technet.microsoft.com/en-us/library/ms126702.aspx">http://technet.microsoft.com/en-us/library/ms126702.aspx</a>), so</font><span style="font-family:arial,sans-serif"> it should be coherent within the same dimension. We had a later issue where just doing it on the xmla layer didn't cut it, and it turned out to be a much simpler change.</span></div>
<div><span style="font-family:arial,sans-serif"><br></span></div><div><span style="font-family:arial,sans-serif">- </span><span style="font-family:arial,sans-serif;font-size:13px">MONDRIAN-1991 - Members by key</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">We only focused on adomd and reporting services, this branch still has issues with excel that we didn't get into. </span><span style="font-size:13px;font-family:arial,sans-serif">It does pass the tests for </span><font face="arial, sans-serif">MONDRIAN-951 apart from the null key that still has to be fixed.</font></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div><span style="font-family:arial,sans-serif;font-size:13px">-</span><span style="font-size:13px;font-family:arial,sans-serif"> MONDRIAN-1993 - </span><span class="" style="font-size:13px;font-family:arial,sans-serif">Xmla</span><span style="font-size:13px;font-family:arial,sans-serif"> exceptions</span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif"> There is a NamespaceCompatibility attribute; although I couldn't find out what it's for, is always used by ms clients and nothing else afaik. However this is only sent when beginning the session, so we'd need proper session tracking before being able to use that.</span></div>
<div><span style="font-size:13px;font-family:arial,sans-serif"> There is an alternative, since mondrian clients expect <error>, adomd expects <Error> and xml is case-sensitive. The property can just add the adomd-friendly error besides the regular one and properly implemented clients might still be able to get what they want (adomd didn't complain). </span></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On 10 April 2014 21:02, Luc Boudreau <span dir="ltr"><<a href="mailto:lucboudreau@gmail.com" target="_blank">lucboudreau@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px">Hey Tiago,</span></div>
<div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div class="gmail_extra">
<font face="arial, sans-serif">Thanks for the write up. I've been waiting a long time for this. This is very cool work that your team has done.</font></div><div class="gmail_extra"><font face="arial, sans-serif"><br>
</font></div>
<div class="gmail_extra"><font face="arial, sans-serif">My comments are below.</font></div><div class="gmail_extra"><font face="arial, sans-serif"><br></font></div><div class="gmail_extra"><font face="arial, sans-serif">Luc</font></div>
<div class="">
<div class="gmail_extra"><font face="arial, sans-serif"><br></font></div><div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px"> - xmlns prefixes (xmla and cxmla) were removed for adomd</span><br>
</div><div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div></div><div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px">This could cause a lot of problems. Have you tried the olap4j XMLA driver without the namespaces? I suspect that it will break apart. Maybe this should be also a property.</span></div>
<div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px"> - Full hierarchy names</span><span style="font-family:arial,sans-serif;font-size:13px"><br>
</span></div><div class="gmail_extra"><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><div class="gmail_extra"><font face="arial, sans-serif">Isn't this functionally equivalent to </font>mondrian.olap.SsasCompatibleNaming? The way you've described it, it sounds like a part of the code in mondrian doesn't honor the value of that property. If you found a place in the code where this property, once set to true, still doesn't affect the output of unique names and the hierarchy isn't added to the unique name, we should probably fix it there.</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><div style="font-family:arial,sans-serif;font-size:13px"> - MONDRIAN-1991 - Members by key.</div><div style="font-family:arial,sans-serif;font-size:13px"><br></div>
<div style="font-family:arial,sans-serif;font-size:13px">There are clear rules in the MDX specs when resolving names. Is this compatible with Excel as well as SSAS? (Was mondrian the only one which differed on this?) This should probably also be controlled by mondrian.olap.SsasCompatibleNaming.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Note that all the changes related to the SsasCompatibleNaming property become the standard in mondrian 4.X. As of now, mondrian 4 behaves as if it was mondrian 3 with the property on. As a matter of fact, there isn't a property anymore. It will remove some complexity in the code and should be easier to merge.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px"> - MONDRIAN-1993 - Xmla exceptions</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">I don't think we should use a property for this. The only way I think would work nicely is if we send back the correct message according to the client. If we use a property, we can only serve either Excel, or everyone else, but not both. That would be very unfortunate.</div>
</div>
</div>
<br>_______________________________________________<br>
Mondrian mailing list<br>
<a href="mailto:Mondrian@pentaho.org">Mondrian@pentaho.org</a><br>
<a href="http://lists.pentaho.org/mailman/listinfo/mondrian" target="_blank">http://lists.pentaho.org/mailman/listinfo/mondrian</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><div><span style="color:rgb(102,102,102)">Tiago Gomes Ferreira<br></span></div><div><span style="color:rgb(102,102,102)">Webdetails Dev<br><br>
</span></div><div><span style="color:rgb(102,102,102)"><a href="http://www.webdetails.pt" target="_blank">www.webdetails.pt</a></span><br></div></div>
</div>