[Mondrian] Mondrian 4 as a Pentaho Plugin

Tom Barber(Alabs) tom at analytical-labs.com
Fri Jun 27 16:06:25 EDT 2014


Gaa boo, silly OSGI Bundles :P

On 27/06/14 21:05, Luc Boudreau wrote:
>
> Tom,
>
> I think the bridging JDBC driver will also be missing. Let us discuss 
> this internally and we'll see if /how we can open some of this to CE.
>
> On Jun 27, 2014 4:03 PM, "Tom Barber(Alabs)" <tom at analytical-labs.com 
> <mailto:tom at analytical-labs.com>> wrote:
>
>     Absolutely nothing, I can't even tell if its being loaded :)
>
>     On 27/06/14 21:01, Luc Boudreau wrote:
>>
>>     Scratch that. Fragment Host is set correctly. Any errors in the
>>     logs?
>>
>>     On Jun 27, 2014 3:54 PM, "Tom Barber(Alabs)"
>>     <tom at analytical-labs.com <mailto:tom at analytical-labs.com>> wrote:
>>
>>         Right, post dinner, still borked....
>>
>>         Manifest-Version: 1.0
>>
>>         Built-By: bugg
>>         Tool: Bnd-2.1.0.20130426-122213
>>         Bundle-Name: MySQL OSGi JDBC Service
>>         Created-By: Apache Maven Bundle Plugin
>>         Build-Jdk: 1.7.0_55
>>         Bundle-Version: 5.1.0.SNAPSHOT
>>         Bnd-LastModified: 1403897665863
>>         Bundle-ManifestVersion: 2
>>         Bundle-SymbolicName: mysql.mondrian
>>         Archiver-Version: Plexus Archiver
>>         Import-Package: com.mysql.jdbc;version="5.1"
>>         Export-Package: com.mysql.jdbc;version="5.1"
>>         Fragment-Host: mondrian
>>           
>>
>>         Something like that look about right?
>>
>>
>>
>>         Tom
>>
>>
>>         On 27/06/14 16:44, Luc Boudreau wrote:
>>>         Just dropping it in there won't work because OSGI doesn't
>>>         have a way to know that mondrian's bundle depends on your
>>>         driver's bundle.
>>>
>>>         What you do is create a new fragment bundle (a jar with only
>>>         the META-INF stuff) which depends on the driver's bundle but
>>>         injects itself into the mondrian bundle. This should bridge
>>>         the two.
>>>
>>>
>>>         On Fri, Jun 27, 2014 at 11:40 AM, Tom Barber(Alabs)
>>>         <tom at analytical-labs.com <mailto:tom at analytical-labs.com>>
>>>         wrote:
>>>
>>>             Ah yeah Kurtis is correct the Mysql JDBC Driver has the
>>>             osgi headers.
>>>
>>>             We'll I've put it in the fragment_bundles directory and
>>>             I still get the Hive error, any other suggestions?
>>>
>>>             Thanks
>>>
>>>             Tom
>>>
>>>
>>>             On 27/06/14 16:31, Kurtis Walker wrote:
>>>>             Yes, but I think most of them already are.  If the
>>>>             manifest has a Bundle-Name, Bundle-Version, etc, then
>>>>             it is ready for osgi.
>>>>
>>>>             On Fri, 2014-06-27 at 10:24 -0500, Tom Barber(Alabs)
>>>>             wrote:
>>>>>             Hmm thanks for the tip Kurtis, no joy so far. Should I
>>>>>             assume the driver needs osgi'ifying?
>>>>>
>>>>>             Thanks
>>>>>
>>>>>             Tom
>>>>>
>>>>>             On 27/06/14 15:46, Kurtis Walker wrote:
>>>>>
>>>>>>             The hive error is misleading.  It really means that
>>>>>>             no JDBC driver could be found to satisfy your connect
>>>>>>             string.  I think you'll need to put your driver in
>>>>>>             the OSGI directory also.
>>>>>>
>>>>>>             On Fri, 2014-06-27 at 09:33 -0500, Tom Barber(Alabs)
>>>>>>             wrote:
>>>>>>>             Looks about right, thanks Luc, Mondrian + Commons IO
>>>>>>>             needed placing in the osgi directory.....
>>>>>>>
>>>>>>>             Now if only I knew why on earth its trying to use
>>>>>>>             Hive to connect....
>>>>>>>
>>>>>>>             On 27/06/14 14:11, Luc Boudreau wrote:
>>>>>>>
>>>>>>>>             Oh right. That'd be in the EE builds only I'm afraid.
>>>>>>>>
>>>>>>>>             The modules should be in solutions/system/osgi
>>>>>>>>
>>>>>>>>             On Jun 27, 2014 8:59 AM, "Tom Barber(Alabs)"
>>>>>>>>             <tom at analytical-labs.com
>>>>>>>>             <mailto:tom at analytical-labs.com>> wrote:
>>>>>>>>
>>>>>>>>                 Interesting Luc, you mean should work out of
>>>>>>>>                 the box, as in, there is already a jar there?
>>>>>>>>
>>>>>>>>                 I downloaded 5.1 and had a look, the Mondrian
>>>>>>>>                 Jar I found(grep) was labeled 3.7 and I asked
>>>>>>>>                 Pedro and he said there were some Mondrian 4
>>>>>>>>                 stuff for Mongo but not in general population.
>>>>>>>>
>>>>>>>>                 Tom
>>>>>>>>
>>>>>>>>                 On 27/06/14 13:50, Luc Boudreau wrote:
>>>>>>>>
>>>>>>>>>                 Hello Tom,
>>>>>>>>>
>>>>>>>>>                 With a 5.1 server, all you need to do is use
>>>>>>>>>                 "jdbc:mondrian4" instead of "jdbc:mondrian" as
>>>>>>>>>                 the URL prefix and it should work out of the box.
>>>>>>>>>
>>>>>>>>>                 Let us know if you run into any issues.
>>>>>>>>>
>>>>>>>>>                 Luc
>>>>>>>>>
>>>>>>>>>                 On Jun 27, 2014 6:38 AM, "Tom Barber(Alabs)"
>>>>>>>>>                 <tom at analytical-labs.com
>>>>>>>>>                 <mailto:tom at analytical-labs.com>> wrote:
>>>>>>>>>
>>>>>>>>>                     Alright chaps,
>>>>>>>>>
>>>>>>>>>                     I'm trying to crowbar Mondrian 4 into the
>>>>>>>>>                     BI Server Saiku plugin and I
>>>>>>>>>                     would like some clarification of a few
>>>>>>>>>                     bits and pieces.
>>>>>>>>>
>>>>>>>>>                     We've shipped our own Mondrian Jar and
>>>>>>>>>                     also done some funky cache
>>>>>>>>>                     sharing etc, anyway, I would like to ship
>>>>>>>>>                     Mondrian 4 and unsurprisingly
>>>>>>>>>                     its not as simple as just replacing the Jar.
>>>>>>>>>
>>>>>>>>>                     I would like to know
>>>>>>>>>
>>>>>>>>>                     a) is it even possible? I saw Julian's
>>>>>>>>>                     slide suggesting that the
>>>>>>>>>                     Mondrian 4 lib should run happily
>>>>>>>>>                     alongside Mondrian 3 as an OSGI module.
>>>>>>>>>                     b) To bootstrap Mondrian we currently run
>>>>>>>>>                      Class.forName(
>>>>>>>>>                     "mondrian.olap4j.MondrianOlap4jDriver" );
>>>>>>>>>                     but if have 2 Jars, how does
>>>>>>>>>                     is it supposed to know which to bootstrap,
>>>>>>>>>                     or should it load Mondrian 3,
>>>>>>>>>                     but Mondrian 4 be automatic or do I have
>>>>>>>>>                     to register the Mondrian 4 jar
>>>>>>>>>                     in a different manner?
>>>>>>>>>                     Either way I get
>>>>>>>>>                     java.lang.IllegalAccessError: class
>>>>>>>>>                     mondrian.olap4j.MondrianOlap4jExtra
>>>>>>>>>                     cannot access its superclass
>>>>>>>>>                     mondrian.xmla.XmlaHandler$XmlaExtraImpl
>>>>>>>>>
>>>>>>>>>                     The first time I try and run Saiku followed by
>>>>>>>>>                     java.lang.NoClassDefFoundError: Could not
>>>>>>>>>                     initialize class
>>>>>>>>>                     mondrian.olap4j.MondrianOlap4jDriver
>>>>>>>>>
>>>>>>>>>                     The next time, so I need work out how to
>>>>>>>>>                     unclash them if possible.
>>>>>>>>>
>>>>>>>>>                     I tried just straight replacing Mondrian 3
>>>>>>>>>                     with Mondrian 4 in the
>>>>>>>>>                     platform out of curiosity but with that I
>>>>>>>>>                     get a linkage error so that
>>>>>>>>>                     test was also a no go.
>>>>>>>>>
>>>>>>>>>                     Anyway, hints or tips please.
>>>>>>>>>
>>>>>>>>>                     Thanks
>>>>>>>>>
>>>>>>>>>                     Tom
>>>>>>>>>                     _______________________________________________
>>>>>>>>>                     Mondrian mailing list
>>>>>>>>>                     Mondrian at pentaho.org
>>>>>>>>>                     <mailto:Mondrian at pentaho.org>
>>>>>>>>>                     http://lists.pentaho.org/mailman/listinfo/mondrian
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>                 _______________________________________________
>>>>>>>>>                 Mondrian mailing list
>>>>>>>>>                 Mondrian at pentaho.org  <mailto:Mondrian at pentaho.org>
>>>>>>>>>                 http://lists.pentaho.org/mailman/listinfo/mondrian
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>                 _______________________________________________
>>>>>>>>                 Mondrian mailing list
>>>>>>>>                 Mondrian at pentaho.org <mailto:Mondrian at pentaho.org>
>>>>>>>>                 http://lists.pentaho.org/mailman/listinfo/mondrian
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>             _______________________________________________
>>>>>>>>             Mondrian mailing list
>>>>>>>>             Mondrian at pentaho.org  <mailto:Mondrian at pentaho.org>
>>>>>>>>             http://lists.pentaho.org/mailman/listinfo/mondrian
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>             _______________________________________________
>>>>>>             Mondrian mailing list
>>>>>>             Mondrian at pentaho.org  <mailto:Mondrian at pentaho.org>
>>>>>>             http://lists.pentaho.org/mailman/listinfo/mondrian
>>>>>
>>>>
>>>>
>>>>
>>>>             _______________________________________________
>>>>             Mondrian mailing list
>>>>             Mondrian at pentaho.org  <mailto:Mondrian at pentaho.org>
>>>>             http://lists.pentaho.org/mailman/listinfo/mondrian
>>>
>>>
>>>             _______________________________________________
>>>             Mondrian mailing list
>>>             Mondrian at pentaho.org <mailto:Mondrian at pentaho.org>
>>>             http://lists.pentaho.org/mailman/listinfo/mondrian
>>>
>>>
>>>
>>>
>>>         _______________________________________________
>>>         Mondrian mailing list
>>>         Mondrian at pentaho.org  <mailto:Mondrian at pentaho.org>
>>>         http://lists.pentaho.org/mailman/listinfo/mondrian
>>
>>
>>         _______________________________________________
>>         Mondrian mailing list
>>         Mondrian at pentaho.org <mailto:Mondrian at pentaho.org>
>>         http://lists.pentaho.org/mailman/listinfo/mondrian
>>
>>
>>
>>     _______________________________________________
>>     Mondrian mailing list
>>     Mondrian at pentaho.org  <mailto:Mondrian at pentaho.org>
>>     http://lists.pentaho.org/mailman/listinfo/mondrian
>
>
>     _______________________________________________
>     Mondrian mailing list
>     Mondrian at pentaho.org <mailto: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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20140627/e6ee028b/attachment-0001.html 


More information about the Mondrian mailing list