#81 XMLA driver should encode colons in property names

Future Release
open
nobody
None
1
2013-10-03
2013-04-08
Julian Hyde
No

XMLA driver should encode colons in property names.

See https://sourceforge.net/p/olap4j/discussion/577988/thread/6a690a3c/ and http://jira.pentaho.com/browse/PRD-3825

"::PENTAHO-REPORTING::PORT" is actually a valid XML element name, but SSAS doesn't think so, and they write the SSAS standard. So the olap4j XMLA driver should convert each colon to 'x003a'.

Discussion

  • Julian Hyde
    Julian Hyde
    2013-04-08

    I meant 'underscore x003a underscore' above. Markdown screwed up my comment.

     
  • Julian Hyde
    Julian Hyde
    2013-04-10

    We should encode non-alphanumeric characters in properties.

    Microsoft does not specify that is a valid property name, but their built-in properties are all UpperCamelCase; see http://msdn.microsoft.com/en-us/library/ms186627.aspx.

    I STRONGLY recommend that people adhere to that standard for property names. (Start with alpha, subsequent characters alphanumeric.) Even underscores will cause problems, because we will encode _ to 0x005f and that may confuse the server receiving the request.

     
  • Luc Boudreau
    Luc Boudreau
    2013-10-03

    This is probably not a problem anymore. We filter out the unknown properties.

     
  • Luc Boudreau
    Luc Boudreau
    2013-10-03

    • Group: olap4j-1.1 --> Future Release