[Olap4j-devel] PALO + olap4j

[Paul S. <pau...@as...>]

Hello,

 

I just did another few test queries on my PALO System with PAT and i’ve
discovered a problem in olap4j / PALO compatibility.

 

In PAT I’m listing all Levels in a Dimension and use their unique name for
further processing.

Unfortunately these unique names don’t look like the ones coming from
Mondrian / SAP BW / SSAS XMLA.

 

For Example in the PALO Demo the Order Cube has a Dimension called MONTHS
and for the MDSCHEMA_LEVELS request I get unique names looking like:

UNIQUE_NAME : [Months].Level00

 

While on other system this unique name would look like:

UNIQUE_NAME : [Months].[Level00]

 

I don’t really know if the standard states that unique names should follow
the schema [x].[y] or not.

But in olap4j I use the QueryDimension.getNameParts(“[Months].Level00”)
which runs into an exception when parsing the Segments in
IdentifierNode.java : parseIdentifier(String identifier) at line 217-219

 

So my question is if we should make the parser more tolerant against unique
names or if PALO is not following the standard here?

 

Thanks in advance for feedback

 

-    Paul