Hi Divye, Can you see the sql which is converted from MDX? Kylin currently supports ANSI SQL only. So, if the converted SQL is not ANSI means it will shout error.
If possible, directly give that sql query in kylin and check whether the problem in sql query side or not. Thanks, Parkavi. -----Original Message----- From: divye sheth [mailto:[email protected]] Sent: Wednesday, May 20, 2015 4:46 PM To: [email protected] Subject: Re: Modrian with Kylin I am trying to access Kylin with MDX. AFAIK Mondrian will convert the MDX into SQL and fire it. I believe it is achievable and found out this link https://github.com/mustangore/thesis/tree/master This integration is of Kylin with Pentaho. I think I am missing the json model similar to the model used for connecting mondrian with mongo explained here " http://julianhyde.blogspot.in/2013/06/efficient-sql-queries-on-mongodb.html ". Also I may have to write a custom schemaFactory for Kylin, is this a correct assumption? Thanks Divye Sheth On Wed, May 20, 2015 at 3:36 PM, dong wang <[email protected]> wrote: > Also very interested in this topic, i vaguely remember that mondrian > supports both SQL and MDX, do you access KYLIN through SQL or MDX > since it seems that KYLIN only supports SQL currently~ > > 2015-05-20 17:47 GMT+08:00 divye sheth <[email protected]>: > > > Hi Devs, > > > > I am trying to get Mondrian to run over Kylin but get an exception > > while creating a connection to Kylin via Mondrian below are the > > steps that I > have > > followed: > > > > 1. Setup Kylin using On-hadoop Install 2. Execute the ./sample.sh > > script to create sample cube in Kylin 3. Build Cube 4. Test queries > > against the cube. Also tested using JDBC driver. > > > > But when I try to execute MDX using Mondrian on top of Kylin I get > > an exception trace as follows: > > *[Mondrian Monitor]:[2015-05-20 > > > 14:55:34,563][DEBUG][mondrian.server.MonitorImpl$Actor.run(MonitorImpl > .java:975)] > > - StatementEndEvent(0)* > > *java.lang.RuntimeException: cannot convert to long > > (net.hydromatic.optiq.runtime.AbstractCursor$StringAccessor@fff056c) > > * > > * at > > > net.hydromatic.optiq.runtime.AbstractCursor$AccessorImpl.cannotConvert > (AbstractCursor.java:287)* > > * at > > > net.hydromatic.optiq.runtime.AbstractCursor$AccessorImpl.getLong(Abstr > actCursor.java:243)* > > * at > > > net.hydromatic.optiq.runtime.AbstractCursor$AccessorImpl.getInt(Abstra > ctCursor.java:239)* > > * at > > > net.hydromatic.avatica.AvaticaResultSet.getInt(AvaticaResultSet.java:2 > 20)* > > * at > > > org.apache.commons.dbcp.DelegatingResultSet.getInt(DelegatingResultSet > .java:225)* > > * at > > > mondrian.rolap.aggmatcher.JdbcSchema$Table.loadColumns(JdbcSchema.java > :972)* > > * at > mondrian.rolap.aggmatcher.JdbcSchema$Table.load(JdbcSchema.java:775)* > > * at > > > mondrian.rolap.RolapSchema$PhysTable.populateColumns(RolapSchema.java: > 1853)* > > * at > > > mondrian.rolap.RolapSchema$PhysRelationImpl.ensurePopulated(RolapSchem > a.java:1519)* > > * at > > > mondrian.rolap.RolapSchema$PhysTable.ensurePopulated(RolapSchema.java: > 1729)* > > * at > > > mondrian.rolap.RolapSchemaLoader.registerTable(RolapSchemaLoader.java: > 1051)* > > * at > > > mondrian.rolap.RolapSchemaLoader.validatePhysicalSchema(RolapSchemaLoa > der.java:715)* > > * at > > mondrian.rolap.RolapSchemaLoader.loadStage2(RolapSchemaLoader.java:3 > > 76)* > > * at > > mondrian.rolap.RolapSchemaLoader.loadStage1(RolapSchemaLoader.java:3 > > 36)* > > * at > > mondrian.rolap.RolapSchemaLoader.loadStage0(RolapSchemaLoader.java:2 > > 72)* > > * at > > > mondrian.rolap.RolapSchemaLoader.createSchema(RolapSchemaLoader.java:4 > 303)* > > * at mondrian.rolap.RolapSchemaPool.get(RolapSchemaPool.java:210)* > > * at mondrian.rolap.RolapSchemaPool.get(RolapSchemaPool.java:62)* > > * at > > mondrian.rolap.RolapConnection.<init>(RolapConnection.java:160)* > > * at mondrian.rolap.RolapConnection.<init>(RolapConnection.java:84)* > > * at > > mondrian.olap.DriverManager.getConnection(DriverManager.java:112)* > > * at > > mondrian.olap.DriverManager.getConnection(DriverManager.java:68)* > > * at > > > mondrian.olap4j.MondrianOlap4jConnection.<init>(MondrianOlap4jConnecti > on.java:153)* > > * at > > > mondrian.olap4j.FactoryJdbc4Plus$AbstractConnection.<init>(FactoryJdbc > 4Plus.java:323)* > > * at > > > mondrian.olap4j.FactoryJdbc41Impl$MondrianOlap4jConnectionJdbc41.<init > >(FactoryJdbc41Impl.java:118)* > > * at > > > mondrian.olap4j.FactoryJdbc41Impl.newConnection(FactoryJdbc41Impl.java > :32)* > > * at > > > mondrian.olap4j.MondrianOlap4jDriver.connect(MondrianOlap4jDriver.java > :139)* > > * at java.sql.DriverManager.getConnection(DriverManager.java:571)* > > * at java.sql.DriverManager.getConnection(DriverManager.java:233)* > > * at > com.fractal.mondrian.kylin.MondrianKylin.main(MondrianKylin.java:27)* > > > > I tried searching a lot but the only link I could find related to > > this issue was > > > > > https://groups.google.com/forum/#!searchin/optiq-dev/mondrian/optiq-de > v/qMd5FyOtp28/-BBsC4ScKe0J > > > > *Kylin Version: 0.7-1* > > *Hadoop: 2.6* > > *Hbase: 0.98* > > *Hive: 1.0.1* > > *Mondrian Jar: 4.3* > > > > Attached is the mondrian xml for reference that corresponds to the > > cube > in > > Kylin. > > I am not pretty sure what am I doing wrong, any help/pointers would > > be appreciated a lot. Apologize if this is not a Kylin issue. > > > > I am new to the Kylin community. > > > > Thanks > > Divye Sheth > > > ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ----------------------------------------------------------------------------------------------------------------------------------------------------
