[prev in list] [next in list] [prev in thread] [next in thread]
List: mondrian
Subject: Re: [Mondrian] XmlaExtra - Mondrian3 vs Mondrian4
From: Julian Hyde <jhyde () pentaho ! com>
Date: 2013-09-18 17:24:50
Message-ID: 1289BEFD-4D70-45B3-9663-75ACCAE759ED () pentaho ! com
[Download RAW message or body]
On Sep 17, 2013, at 10:04 PM, Benny Chow <bchow@pentaho.com<mailto:bchow@pe=
ntaho.com>> wrote:
I=92m looking into how we could support Analyzer on Mondrian4.
In Mondrian4, it seems a lot of the olap4j integration code was moved to ol=
ap4j-xmlaserver.jar.
Can someone explain the basis for moving this out of core mondrian?
The XMLA server was a large body of code that depended only loosely on Mond=
rian, but strongly on olap4j. It made sense to make it a separate module, a=
nd replace the "back door" with official APIs in olap4j version 2.
Some contributors want to make an XMLA server that spoke to an olap4j data =
source that is not Mondrian. This makes perfect sense, and now that olap4j-=
xmlaserver is a separate project it is now possible.
Now the more important issue=85 There=92s some functionality that Analyzer =
depends on in the below class that is not present in Mondrian 4 now:
http://mondrian.pentaho.com/api/mondrian/xmla/XmlaHandler.XmlaExtra.html
XmlaExtra is the "back door" I was referring to. It is one of the goals of =
the olap4j 2.0 project to get rid of it. (See discussions on that list.)
I don't want to add XmlaExtra back into lagunitas now it has gone. If you r=
eally must, you can add it back in a branch off of lagnitas. But better to =
add the APIs you need into the new olap4j interface.
Julian
[Attachment #3 (text/html)]
<html><head><meta http-equiv="Content-Type" content="text/html \
charset=windows-1252"><base href="x-msg://512/"></head><body style="word-wrap: \
break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; \
"><div><div>On Sep 17, 2013, at 10:04 PM, Benny Chow <<a \
href="mailto:bchow@pentaho.com">bchow@pentaho.com</a>> wrote:</div><br \
class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-US" \
link="blue" vlink="purple" style="font-family: Helvetica; font-size: medium; \
font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: \
normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; \
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; \
-webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div \
class="WordSection1" style="page: WordSection1; "><div style="margin: 0in 0in \
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">I’m looking into how \
we could support Analyzer on Mondrian4. <o:p></o:p></div><div style="margin: 0in \
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; \
"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; \
font-family: Calibri, sans-serif; ">In Mondrian4, it seems a lot of the olap4j \
integration code was moved to olap4j-xmlaserver.jar. <o:p></o:p></div><div \
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; \
"><o:p> </o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; \
font-family: Calibri, sans-serif; ">Can someone explain the basis for moving this out \
of core mondrian?</div></div></div></blockquote><div><br></div>The XMLA server was a \
large body of code that depended only loosely on Mondrian, but strongly on olap4j. It \
made sense to make it a separate module, and replace the "back door" with official \
APIs in olap4j version 2.</div><div><br></div><div>Some contributors want to make an \
XMLA server that spoke to an olap4j data source that is not Mondrian. This makes \
perfect sense, and now that olap4j-xmlaserver is a separate project it is now \
possible.</div><div><br><blockquote type="cite"><div lang="EN-US" link="blue" \
vlink="purple" style="font-family: Helvetica; font-size: medium; font-style: normal; \
font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: \
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; \
white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; \
-webkit-text-stroke-width: 0px; "><div class="WordSection1" style="page: \
WordSection1; "><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: \
Calibri, sans-serif; "><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; \
font-size: 11pt; font-family: Calibri, sans-serif; "><span style="font-size: 11pt; \
">Now the more important issue… There’s some functionality that Analyzer depends on \
in the below class that is not present in Mondrian 4 now:</span></div><div \
style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; \
"><o:p></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; \
font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0in \
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><a \
href="http://mondrian.pentaho.com/api/mondrian/xmla/XmlaHandler.XmlaExtra.html" \
style="color: purple; text-decoration: underline; \
">http://mondrian.pentaho.com/api/mondrian/xmla/XmlaHandler.XmlaExtra.html</a></div></div></div></blockquote><div><br></div>XmlaExtra \
is the "back door" I was referring to. It is one of the goals of the olap4j 2.0 \
project to get rid of it. (See discussions on that list.)</div><div><br></div><div>I \
don't want to add XmlaExtra back into lagunitas now it has gone. If you really must, \
you can add it back in a branch off of lagnitas. But better to add the APIs you need \
into the new olap4j interface.</div><div><br></div><div>Julian</div><div><br></div></body></html>
_______________________________________________
Mondrian mailing list
Mondrian@pentaho.org
http://lists.pentaho.org/mailman/listinfo/mondrian
--===============0423506580656927794==--
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic