[ https://jira.jboss.org/browse/TEIID-1011?page=com.atlassian.jira.plugin.s... ] Steve Hawkins updated TEIID-1011: --------------------------------- Fix Version/s: 7.2 (was: 7.1) Pushing to 7.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1011?page=com.atlassian.jira.plugin... ] Ramesh Reddy reassigned TEIID-1011: ----------------------------------- Assignee: Ramesh Reddy (was: Steven Hawkins) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1011?page=com.atlassian.jira.plugin... ] John Doyle commented on TEIID-1011: ----------------------------------- I think you are mistaken about the jdbc4olap driver. I tested it with MetaMatrix several releases ago using a SAP BW server. It creates a virtual star schema from the cube, and takes SQL queries that it converts to MDX queries for the source system. It is limited to OLAP servers that support XMLA. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1011?page=com.atlassian.jira.plugin... ] Steven Hawkins updated TEIID-1011: ---------------------------------- Fix Version/s: 7.4 (was: 7.3) pushing to 7.4. Upon further analysis with Ramesh we see two possible approaches: 1. just leverage soap functionality. extraction from tabular results would be quite easy with xmltable. some wrappering could be added that makes this almost as easy as mdx in, and rows out. 2. use jdbc4olap, or olap4j, or a custom approach, that would need a set of functions and tabular metadata to issue MDX like queries. This however would provide little abstraction value (you would issue something like "SELECT ONCOLUMN(DIM.LEVEL) ..." where the metadata for the dimension table serves no purpose other than to form the MDX-like queries). It also would be require potentially a large set of functions to provide the functionality of MDX. Given those alternatives we're leaning toward #1, which is currently doable without a custom translator. It would be good for Ken to weigh in on what intended use case would be for this integration. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1011?page=com.atlassian.jira.plugin... ] John Doyle commented on TEIID-1011: ----------------------------------- SAP does support XMLA. But I do think it's important for Ken to comment before this is closed. The ability to parse the values out of an XMLA response still leave a large conceptual gap for the implementer to resolve (it's still multidimensional). That said, in my discussions with users interested in OLAP and specifically SAP BW connectivity they want it as a check box item, but can't provide a use case. So it's hard to know what's satisfactory. I'm concerned this solution might check the box but be considered too complex when a user attempts to use it. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIID-1011?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-1011. ----------------------------------- Resolution: Done Marking as resolved. The approach has some overlap with TEIID-669, since we are directly allowing mdx. Will add a note to the reference that the invoke procedure may need to have restricted access. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira