[Mondrian] sharing mondrian cache with biserver

Julian Hyde jhyde at pentaho.com
Wed Jun 6 19:58:34 EDT 2012

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.


More information about the Mondrian mailing list