[Mondrian] sharing mondrian cache with biserver

Pedro Alves pmgalves at gmail.com
Wed Jun 6 20:10:43 EDT 2012

Don't get me wrong, I'm not saying olap4j is wrong nor advocating hacks!
I'm trying to get solutions, preferably with tools we currently have

I'M open to suggestions!

On Thursday, June 7, 2012, Julian Hyde wrote:

> On Jun 6, 2012, at 4:35 PM, Pedro Alves wrote:
> > We were able to get saiku using the same mondrian engine as pentaho,
> taking advantage of cdc...
> >
> > ... To discover that 2 queries in prd/jpivot/analyzer/xaction/kettle and
> saiku don't share cache keys.
> >
> > In my simplistic view, we can either change olap4j or
> prd/jpivot/analyzer/xaction/kettle :)
> Your reasoning is suspect. Just because olap4j is the easiest thing to
> change doesn't mean it's at fault.
> olap4j uses the same connection management process as JDBC. In fact, it is
> JDBC. I know there are issues with connection identity. Every database
> driver that ever existed has had them. As soon as everyone is using olap4j,
> we can improve the olap4j driver to iron out the connection identity issues.
> If you think I'm going to drill holes in olap4j's connection management
> model so you can introduce short-term hacks, you are mistaken.
> Julian
> _______________________________________________
> Mondrian mailing list
> Mondrian at pentaho.org <javascript:;>
> http://lists.pentaho.org/mailman/listinfo/mondrian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pentaho.org/pipermail/mondrian/attachments/20120607/4cc08e00/attachment.html 

More information about the Mondrian mailing list