You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kylin.apache.org by Sébastien Jelsch <sj...@inovex.de> on 2015/06/08 12:12:20 UTC

Re: Modrian with Kylin

I found the reason for this issue ( https://issues.apache.org/jira/browse/KYLIN-819 ) and fixed it ( https://github.com/apache/incubator-kylin/pull/9/files ).

Best Regards,
Sébastien Jelsch



> Am 22.05.2015 um 18:33 schrieb Luke Han <lu...@gmail.com>:
> 
> Please handle this part to Shanghai team, I will put this story in v0.7.2
> (after successful release v0.7.1).
> 
> Thanks.
> 
> 
> Best Regards!
> ---------------------
> 
> Luke Han
> 
> 2015-05-23 0:25 GMT+08:00 divye sheth <di...@gmail.com>:
> 
>> Will wait for the core committers. In the meantime might as well test kylin
>> with 0.9.2.
>> 
>> Thanks!
>> On May 22, 2015 21:52, "Julian Hyde" <jh...@apache.org> wrote:
>> 
>>> Calcite 0.9.2 -> 1.0 is a tricky upgrade. I think you should leave it to
>>> the core committers.
>>> 
>>> I wouldn't even be sure that the upgrade from 0.9.1 to 0.9.2 worked until
>>> the tests had passed.
>>> 
>>> On Fri, May 22, 2015 at 9:11 AM, divye sheth <di...@gmail.com>
>> wrote:
>>> 
>>>> The 0.9.2 release builds fine with Kylin (just built kylin have not
>>>> tested). With the Calcite 1.0 release there have been significant
>>>> class/package renaming and movement as well as some additional classes
>>>> coming in. Currently I am trying to figure out AvaticaPrepareResult ->
>>>> Meta.Signature
>>>> I am trying my best here. Java is something that I am not that strong
>>> with
>>>> :-)
>>>> 
>>>> Thanks
>>>> Divye Sheth
>>>> On May 22, 2015 21:12, "Julian Hyde" <jh...@apache.org> wrote:
>>>> 
>>>>> There are significant API changes between Calcite 0.9 and 1.0. Read
>> the
>>>> 1.0
>>>>> release notes
>>>>> 
>>>>> 
>>>> 
>>> 
>> https://github.com/apache/incubator-calcite/blob/branch-1.3/doc/history.md#100-incubating--2015-01-31
>>>>> ,
>>>>> and use the API mapping
>>>>> 
>> https://issues.apache.org/jira/secure/attachment/12681620/mapping.txt
>>> if
>>>>> you need to. Consider upgrading to 0.9.2 (the last release with the
>> old
>>>>> API) and getting that working before moving to the renamed API.
>>>>> 
>>>>> I've logged https://issues.apache.org/jira/browse/KYLIN-780 to track
>>>> this.
>>>>> 
>>>>> 
>>>>> On Thu, May 21, 2015 at 9:51 PM, divye sheth <di...@gmail.com>
>>>> wrote:
>>>>> 
>>>>>> Thanks Julian, will try porting optiq 0.9 to calcite 1.0. Will
>> commit
>>>> if
>>>>>> successfull.
>>>>>> 
>>>>>> Thanks
>>>>>> Divye Sheth
>>>>>> On May 21, 2015 22:18, "Julian Hyde" <jh...@apache.org> wrote:
>>>>>> 
>>>>>>> It seems that Mondrian is trying to access a string column as if
>> it
>>>>> were
>>>>>> a
>>>>>>> long. Maybe you declared the column of the wrong type in your
>>>> Mondrian
>>>>>>> schema file? Or maybe Kylin is not reporting the type accurately.
>>>>>>> 
>>>>>>> The JDBC driver code that is failing to convert (
>>>>>>> *net.hydromatic.optiq.runtime.AbstractCursor*) is in Optiq, now
>>>> called
>>>>>>> Calcite. Later versions of Calcite are more permissive about
>>>>> conversions
>>>>>> so
>>>>>>> if Kylin upgraded to a more recent version of Calcite that would
>>>>> probably
>>>>>>> improve things.
>>>>>>> 
>>>>>>> On Wed, May 20, 2015 at 2:47 AM, divye sheth <
>> divs.sheth@gmail.com
>>>> 
>>>>>> wrote:
>>>>>>> 
>>>>>>>> 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(AbstractCursor.java:243)*
>>>>>>>> * at
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> net.hydromatic.optiq.runtime.AbstractCursor$AccessorImpl.getInt(AbstractCursor.java:239)*
>>>>>>>> * at
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> net.hydromatic.avatica.AvaticaResultSet.getInt(AvaticaResultSet.java:220)*
>>>>>>>> * 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(RolapSchema.java:1519)*
>>>>>>>> * at
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> mondrian.rolap.RolapSchema$PhysTable.ensurePopulated(RolapSchema.java:1729)*
>>>>>>>> * at
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> mondrian.rolap.RolapSchemaLoader.registerTable(RolapSchemaLoader.java:1051)*
>>>>>>>> * at
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> mondrian.rolap.RolapSchemaLoader.validatePhysicalSchema(RolapSchemaLoader.java:715)*
>>>>>>>> * at
>>>>>>>> 
>>>>>> 
>>>> 
>> mondrian.rolap.RolapSchemaLoader.loadStage2(RolapSchemaLoader.java:376)*
>>>>>>>> * at
>>>>>>>> 
>>>>>> 
>>>> 
>> mondrian.rolap.RolapSchemaLoader.loadStage1(RolapSchemaLoader.java:336)*
>>>>>>>> * at
>>>>>>>> 
>>>>>> 
>>>> 
>> mondrian.rolap.RolapSchemaLoader.loadStage0(RolapSchemaLoader.java:272)*
>>>>>>>> * at
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> mondrian.rolap.RolapSchemaLoader.createSchema(RolapSchemaLoader.java:4303)*
>>>>>>>> * 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>(MondrianOlap4jConnection.java:153)*
>>>>>>>> * at
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> mondrian.olap4j.FactoryJdbc4Plus$AbstractConnection.<init>(FactoryJdbc4Plus.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-dev/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
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 


Re: Modrian with Kylin

Posted by Luke Han <lu...@gmail.com>.
Awesome Sébastien!

We will take a look and merge our pull request and include in 0.7.2 release.

Could you please help to draft the how to doc for others to refer?

Thank you very much.



Best Regards!
---------------------

Luke Han

2015-06-08 10:13 GMT-07:00 Sébastien Jelsch <se...@inovex.de>:

> Hi Divye,
>
> you can download my mondrian lagunitas snapshot with added kylin dialect
> and give it a try:
> https://github.com/mustangore/thesis/tree/master/Mondrian <
> https://github.com/mustangore/thesis/tree/master/Mondrian>
>
> Best regards,
> Sébastien Jelsch
>
>
>
> > Am 08.06.2015 um 17:43 schrieb divye sheth <di...@gmail.com>:
> >
> > I was referring to the latest stack trace of the eigenbase exception. I
> > think i have goofed up a little in the previous mail. Will build
> > mondrian-jdbc jar from the specified branch and will post the results.
> >
> > Thanks!
> > Divye Sheth
> > On Jun 8, 2015 9:08 PM, "divye sheth" <di...@gmail.com> wrote:
> >
> >> Thanks Sebastian, I am using Mondrian 4 but not the branch you
> mentioned.
> >> I have checked out the branch and will be building the mondrian jar, the
> >> build.sh script does not make the jar. Will checkout the new kylin
> branch
> >> and build again. Just for my info, what caused this issue?
> >>
> >> Thank!
> >> Divye Sheth
> >> On Jun 8, 2015 20:25, "Sébastien Jelsch" <sj...@inovex.de> wrote:
> >>
> >>> I found the reason for this issue (
> >>> https://issues.apache.org/jira/browse/KYLIN-819 ) and fixed it (
> >>> https://github.com/apache/incubator-kylin/pull/9/files ).
> >>>
> >>> Best Regards,
> >>> Sébastien Jelsch
> >>>
> >>>
> >>>
> >>>> Am 22.05.2015 um 18:33 schrieb Luke Han <lu...@gmail.com>:
> >>>>
> >>>> Please handle this part to Shanghai team, I will put this story in
> >>> v0.7.2
> >>>> (after successful release v0.7.1).
> >>>>
> >>>> Thanks.
> >>>>
> >>>>
> >>>> Best Regards!
> >>>> ---------------------
> >>>>
> >>>> Luke Han
> >>>>
> >>>> 2015-05-23 0:25 GMT+08:00 divye sheth <di...@gmail.com>:
> >>>>
> >>>>> Will wait for the core committers. In the meantime might as well test
> >>> kylin
> >>>>> with 0.9.2.
> >>>>>
> >>>>> Thanks!
> >>>>> On May 22, 2015 21:52, "Julian Hyde" <jh...@apache.org> wrote:
> >>>>>
> >>>>>> Calcite 0.9.2 -> 1.0 is a tricky upgrade. I think you should leave
> it
> >>> to
> >>>>>> the core committers.
> >>>>>>
> >>>>>> I wouldn't even be sure that the upgrade from 0.9.1 to 0.9.2 worked
> >>> until
> >>>>>> the tests had passed.
> >>>>>>
> >>>>>> On Fri, May 22, 2015 at 9:11 AM, divye sheth <di...@gmail.com>
> >>>>> wrote:
> >>>>>>
> >>>>>>> The 0.9.2 release builds fine with Kylin (just built kylin have not
> >>>>>>> tested). With the Calcite 1.0 release there have been significant
> >>>>>>> class/package renaming and movement as well as some additional
> >>> classes
> >>>>>>> coming in. Currently I am trying to figure out AvaticaPrepareResult
> >>> ->
> >>>>>>> Meta.Signature
> >>>>>>> I am trying my best here. Java is something that I am not that
> strong
> >>>>>> with
> >>>>>>> :-)
> >>>>>>>
> >>>>>>> Thanks
> >>>>>>> Divye Sheth
> >>>>>>> On May 22, 2015 21:12, "Julian Hyde" <jh...@apache.org> wrote:
> >>>>>>>
> >>>>>>>> There are significant API changes between Calcite 0.9 and 1.0.
> Read
> >>>>> the
> >>>>>>> 1.0
> >>>>>>>> release notes
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> https://github.com/apache/incubator-calcite/blob/branch-1.3/doc/history.md#100-incubating--2015-01-31
> >>>>>>>> ,
> >>>>>>>> and use the API mapping
> >>>>>>>>
> >>>>>
> https://issues.apache.org/jira/secure/attachment/12681620/mapping.txt
> >>>>>> if
> >>>>>>>> you need to. Consider upgrading to 0.9.2 (the last release with
> the
> >>>>> old
> >>>>>>>> API) and getting that working before moving to the renamed API.
> >>>>>>>>
> >>>>>>>> I've logged https://issues.apache.org/jira/browse/KYLIN-780 to
> >>> track
> >>>>>>> this.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Thu, May 21, 2015 at 9:51 PM, divye sheth <
> divs.sheth@gmail.com>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Thanks Julian, will try porting optiq 0.9 to calcite 1.0. Will
> >>>>> commit
> >>>>>>> if
> >>>>>>>>> successfull.
> >>>>>>>>>
> >>>>>>>>> Thanks
> >>>>>>>>> Divye Sheth
> >>>>>>>>> On May 21, 2015 22:18, "Julian Hyde" <jh...@apache.org> wrote:
> >>>>>>>>>
> >>>>>>>>>> It seems that Mondrian is trying to access a string column as if
> >>>>> it
> >>>>>>>> were
> >>>>>>>>> a
> >>>>>>>>>> long. Maybe you declared the column of the wrong type in your
> >>>>>>> Mondrian
> >>>>>>>>>> schema file? Or maybe Kylin is not reporting the type
> accurately.
> >>>>>>>>>>
> >>>>>>>>>> The JDBC driver code that is failing to convert (
> >>>>>>>>>> *net.hydromatic.optiq.runtime.AbstractCursor*) is in Optiq, now
> >>>>>>> called
> >>>>>>>>>> Calcite. Later versions of Calcite are more permissive about
> >>>>>>>> conversions
> >>>>>>>>> so
> >>>>>>>>>> if Kylin upgraded to a more recent version of Calcite that would
> >>>>>>>> probably
> >>>>>>>>>> improve things.
> >>>>>>>>>>
> >>>>>>>>>> On Wed, May 20, 2015 at 2:47 AM, divye sheth <
> >>>>> divs.sheth@gmail.com
> >>>>>>>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> 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(AbstractCursor.java:243)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> net.hydromatic.optiq.runtime.AbstractCursor$AccessorImpl.getInt(AbstractCursor.java:239)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> net.hydromatic.avatica.AvaticaResultSet.getInt(AvaticaResultSet.java:220)*
> >>>>>>>>>>> * 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(RolapSchema.java:1519)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> mondrian.rolap.RolapSchema$PhysTable.ensurePopulated(RolapSchema.java:1729)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> mondrian.rolap.RolapSchemaLoader.registerTable(RolapSchemaLoader.java:1051)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> mondrian.rolap.RolapSchemaLoader.validatePhysicalSchema(RolapSchemaLoader.java:715)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>>
> mondrian.rolap.RolapSchemaLoader.loadStage2(RolapSchemaLoader.java:376)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>>
> mondrian.rolap.RolapSchemaLoader.loadStage1(RolapSchemaLoader.java:336)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>
> >>>
> mondrian.rolap.RolapSchemaLoader.loadStage0(RolapSchemaLoader.java:272)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> mondrian.rolap.RolapSchemaLoader.createSchema(RolapSchemaLoader.java:4303)*
> >>>>>>>>>>> * 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>(MondrianOlap4jConnection.java:153)*
> >>>>>>>>>>> * at
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> mondrian.olap4j.FactoryJdbc4Plus$AbstractConnection.<init>(FactoryJdbc4Plus.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-dev/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
> >>>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>
> >>>
>
>

Re: Modrian with Kylin

Posted by Sébastien Jelsch <se...@inovex.de>.
Hi Divye,

you can download my mondrian lagunitas snapshot with added kylin dialect and give it a try:
https://github.com/mustangore/thesis/tree/master/Mondrian <https://github.com/mustangore/thesis/tree/master/Mondrian>

Best regards,
Sébastien Jelsch



> Am 08.06.2015 um 17:43 schrieb divye sheth <di...@gmail.com>:
> 
> I was referring to the latest stack trace of the eigenbase exception. I
> think i have goofed up a little in the previous mail. Will build
> mondrian-jdbc jar from the specified branch and will post the results.
> 
> Thanks!
> Divye Sheth
> On Jun 8, 2015 9:08 PM, "divye sheth" <di...@gmail.com> wrote:
> 
>> Thanks Sebastian, I am using Mondrian 4 but not the branch you mentioned.
>> I have checked out the branch and will be building the mondrian jar, the
>> build.sh script does not make the jar. Will checkout the new kylin branch
>> and build again. Just for my info, what caused this issue?
>> 
>> Thank!
>> Divye Sheth
>> On Jun 8, 2015 20:25, "Sébastien Jelsch" <sj...@inovex.de> wrote:
>> 
>>> I found the reason for this issue (
>>> https://issues.apache.org/jira/browse/KYLIN-819 ) and fixed it (
>>> https://github.com/apache/incubator-kylin/pull/9/files ).
>>> 
>>> Best Regards,
>>> Sébastien Jelsch
>>> 
>>> 
>>> 
>>>> Am 22.05.2015 um 18:33 schrieb Luke Han <lu...@gmail.com>:
>>>> 
>>>> Please handle this part to Shanghai team, I will put this story in
>>> v0.7.2
>>>> (after successful release v0.7.1).
>>>> 
>>>> Thanks.
>>>> 
>>>> 
>>>> Best Regards!
>>>> ---------------------
>>>> 
>>>> Luke Han
>>>> 
>>>> 2015-05-23 0:25 GMT+08:00 divye sheth <di...@gmail.com>:
>>>> 
>>>>> Will wait for the core committers. In the meantime might as well test
>>> kylin
>>>>> with 0.9.2.
>>>>> 
>>>>> Thanks!
>>>>> On May 22, 2015 21:52, "Julian Hyde" <jh...@apache.org> wrote:
>>>>> 
>>>>>> Calcite 0.9.2 -> 1.0 is a tricky upgrade. I think you should leave it
>>> to
>>>>>> the core committers.
>>>>>> 
>>>>>> I wouldn't even be sure that the upgrade from 0.9.1 to 0.9.2 worked
>>> until
>>>>>> the tests had passed.
>>>>>> 
>>>>>> On Fri, May 22, 2015 at 9:11 AM, divye sheth <di...@gmail.com>
>>>>> wrote:
>>>>>> 
>>>>>>> The 0.9.2 release builds fine with Kylin (just built kylin have not
>>>>>>> tested). With the Calcite 1.0 release there have been significant
>>>>>>> class/package renaming and movement as well as some additional
>>> classes
>>>>>>> coming in. Currently I am trying to figure out AvaticaPrepareResult
>>> ->
>>>>>>> Meta.Signature
>>>>>>> I am trying my best here. Java is something that I am not that strong
>>>>>> with
>>>>>>> :-)
>>>>>>> 
>>>>>>> Thanks
>>>>>>> Divye Sheth
>>>>>>> On May 22, 2015 21:12, "Julian Hyde" <jh...@apache.org> wrote:
>>>>>>> 
>>>>>>>> There are significant API changes between Calcite 0.9 and 1.0. Read
>>>>> the
>>>>>>> 1.0
>>>>>>>> release notes
>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> https://github.com/apache/incubator-calcite/blob/branch-1.3/doc/history.md#100-incubating--2015-01-31
>>>>>>>> ,
>>>>>>>> and use the API mapping
>>>>>>>> 
>>>>> https://issues.apache.org/jira/secure/attachment/12681620/mapping.txt
>>>>>> if
>>>>>>>> you need to. Consider upgrading to 0.9.2 (the last release with the
>>>>> old
>>>>>>>> API) and getting that working before moving to the renamed API.
>>>>>>>> 
>>>>>>>> I've logged https://issues.apache.org/jira/browse/KYLIN-780 to
>>> track
>>>>>>> this.
>>>>>>>> 
>>>>>>>> 
>>>>>>>> On Thu, May 21, 2015 at 9:51 PM, divye sheth <di...@gmail.com>
>>>>>>> wrote:
>>>>>>>> 
>>>>>>>>> Thanks Julian, will try porting optiq 0.9 to calcite 1.0. Will
>>>>> commit
>>>>>>> if
>>>>>>>>> successfull.
>>>>>>>>> 
>>>>>>>>> Thanks
>>>>>>>>> Divye Sheth
>>>>>>>>> On May 21, 2015 22:18, "Julian Hyde" <jh...@apache.org> wrote:
>>>>>>>>> 
>>>>>>>>>> It seems that Mondrian is trying to access a string column as if
>>>>> it
>>>>>>>> were
>>>>>>>>> a
>>>>>>>>>> long. Maybe you declared the column of the wrong type in your
>>>>>>> Mondrian
>>>>>>>>>> schema file? Or maybe Kylin is not reporting the type accurately.
>>>>>>>>>> 
>>>>>>>>>> The JDBC driver code that is failing to convert (
>>>>>>>>>> *net.hydromatic.optiq.runtime.AbstractCursor*) is in Optiq, now
>>>>>>> called
>>>>>>>>>> Calcite. Later versions of Calcite are more permissive about
>>>>>>>> conversions
>>>>>>>>> so
>>>>>>>>>> if Kylin upgraded to a more recent version of Calcite that would
>>>>>>>> probably
>>>>>>>>>> improve things.
>>>>>>>>>> 
>>>>>>>>>> On Wed, May 20, 2015 at 2:47 AM, divye sheth <
>>>>> divs.sheth@gmail.com
>>>>>>> 
>>>>>>>>> wrote:
>>>>>>>>>> 
>>>>>>>>>>> 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(AbstractCursor.java:243)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> net.hydromatic.optiq.runtime.AbstractCursor$AccessorImpl.getInt(AbstractCursor.java:239)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> net.hydromatic.avatica.AvaticaResultSet.getInt(AvaticaResultSet.java:220)*
>>>>>>>>>>> * 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(RolapSchema.java:1519)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> mondrian.rolap.RolapSchema$PhysTable.ensurePopulated(RolapSchema.java:1729)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> mondrian.rolap.RolapSchemaLoader.registerTable(RolapSchemaLoader.java:1051)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> mondrian.rolap.RolapSchemaLoader.validatePhysicalSchema(RolapSchemaLoader.java:715)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>> 
>>> mondrian.rolap.RolapSchemaLoader.loadStage2(RolapSchemaLoader.java:376)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>> 
>>> mondrian.rolap.RolapSchemaLoader.loadStage1(RolapSchemaLoader.java:336)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>> 
>>>>>>> 
>>>>> 
>>> mondrian.rolap.RolapSchemaLoader.loadStage0(RolapSchemaLoader.java:272)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> mondrian.rolap.RolapSchemaLoader.createSchema(RolapSchemaLoader.java:4303)*
>>>>>>>>>>> * 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>(MondrianOlap4jConnection.java:153)*
>>>>>>>>>>> * at
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> mondrian.olap4j.FactoryJdbc4Plus$AbstractConnection.<init>(FactoryJdbc4Plus.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-dev/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
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>> 
>>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>> 
>>> 
>>> 


Re: Modrian with Kylin

Posted by divye sheth <di...@gmail.com>.
I was referring to the latest stack trace of the eigenbase exception. I
think i have goofed up a little in the previous mail. Will build
mondrian-jdbc jar from the specified branch and will post the results.

Thanks!
Divye Sheth
On Jun 8, 2015 9:08 PM, "divye sheth" <di...@gmail.com> wrote:

> Thanks Sebastian, I am using Mondrian 4 but not the branch you mentioned.
> I have checked out the branch and will be building the mondrian jar, the
> build.sh script does not make the jar. Will checkout the new kylin branch
> and build again. Just for my info, what caused this issue?
>
> Thank!
> Divye Sheth
> On Jun 8, 2015 20:25, "Sébastien Jelsch" <sj...@inovex.de> wrote:
>
>> I found the reason for this issue (
>> https://issues.apache.org/jira/browse/KYLIN-819 ) and fixed it (
>> https://github.com/apache/incubator-kylin/pull/9/files ).
>>
>> Best Regards,
>> Sébastien Jelsch
>>
>>
>>
>> > Am 22.05.2015 um 18:33 schrieb Luke Han <lu...@gmail.com>:
>> >
>> > Please handle this part to Shanghai team, I will put this story in
>> v0.7.2
>> > (after successful release v0.7.1).
>> >
>> > Thanks.
>> >
>> >
>> > Best Regards!
>> > ---------------------
>> >
>> > Luke Han
>> >
>> > 2015-05-23 0:25 GMT+08:00 divye sheth <di...@gmail.com>:
>> >
>> >> Will wait for the core committers. In the meantime might as well test
>> kylin
>> >> with 0.9.2.
>> >>
>> >> Thanks!
>> >> On May 22, 2015 21:52, "Julian Hyde" <jh...@apache.org> wrote:
>> >>
>> >>> Calcite 0.9.2 -> 1.0 is a tricky upgrade. I think you should leave it
>> to
>> >>> the core committers.
>> >>>
>> >>> I wouldn't even be sure that the upgrade from 0.9.1 to 0.9.2 worked
>> until
>> >>> the tests had passed.
>> >>>
>> >>> On Fri, May 22, 2015 at 9:11 AM, divye sheth <di...@gmail.com>
>> >> wrote:
>> >>>
>> >>>> The 0.9.2 release builds fine with Kylin (just built kylin have not
>> >>>> tested). With the Calcite 1.0 release there have been significant
>> >>>> class/package renaming and movement as well as some additional
>> classes
>> >>>> coming in. Currently I am trying to figure out AvaticaPrepareResult
>> ->
>> >>>> Meta.Signature
>> >>>> I am trying my best here. Java is something that I am not that strong
>> >>> with
>> >>>> :-)
>> >>>>
>> >>>> Thanks
>> >>>> Divye Sheth
>> >>>> On May 22, 2015 21:12, "Julian Hyde" <jh...@apache.org> wrote:
>> >>>>
>> >>>>> There are significant API changes between Calcite 0.9 and 1.0. Read
>> >> the
>> >>>> 1.0
>> >>>>> release notes
>> >>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> https://github.com/apache/incubator-calcite/blob/branch-1.3/doc/history.md#100-incubating--2015-01-31
>> >>>>> ,
>> >>>>> and use the API mapping
>> >>>>>
>> >> https://issues.apache.org/jira/secure/attachment/12681620/mapping.txt
>> >>> if
>> >>>>> you need to. Consider upgrading to 0.9.2 (the last release with the
>> >> old
>> >>>>> API) and getting that working before moving to the renamed API.
>> >>>>>
>> >>>>> I've logged https://issues.apache.org/jira/browse/KYLIN-780 to
>> track
>> >>>> this.
>> >>>>>
>> >>>>>
>> >>>>> On Thu, May 21, 2015 at 9:51 PM, divye sheth <di...@gmail.com>
>> >>>> wrote:
>> >>>>>
>> >>>>>> Thanks Julian, will try porting optiq 0.9 to calcite 1.0. Will
>> >> commit
>> >>>> if
>> >>>>>> successfull.
>> >>>>>>
>> >>>>>> Thanks
>> >>>>>> Divye Sheth
>> >>>>>> On May 21, 2015 22:18, "Julian Hyde" <jh...@apache.org> wrote:
>> >>>>>>
>> >>>>>>> It seems that Mondrian is trying to access a string column as if
>> >> it
>> >>>>> were
>> >>>>>> a
>> >>>>>>> long. Maybe you declared the column of the wrong type in your
>> >>>> Mondrian
>> >>>>>>> schema file? Or maybe Kylin is not reporting the type accurately.
>> >>>>>>>
>> >>>>>>> The JDBC driver code that is failing to convert (
>> >>>>>>> *net.hydromatic.optiq.runtime.AbstractCursor*) is in Optiq, now
>> >>>> called
>> >>>>>>> Calcite. Later versions of Calcite are more permissive about
>> >>>>> conversions
>> >>>>>> so
>> >>>>>>> if Kylin upgraded to a more recent version of Calcite that would
>> >>>>> probably
>> >>>>>>> improve things.
>> >>>>>>>
>> >>>>>>> On Wed, May 20, 2015 at 2:47 AM, divye sheth <
>> >> divs.sheth@gmail.com
>> >>>>
>> >>>>>> wrote:
>> >>>>>>>
>> >>>>>>>> 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(AbstractCursor.java:243)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> net.hydromatic.optiq.runtime.AbstractCursor$AccessorImpl.getInt(AbstractCursor.java:239)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> net.hydromatic.avatica.AvaticaResultSet.getInt(AvaticaResultSet.java:220)*
>> >>>>>>>> * 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(RolapSchema.java:1519)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> mondrian.rolap.RolapSchema$PhysTable.ensurePopulated(RolapSchema.java:1729)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> mondrian.rolap.RolapSchemaLoader.registerTable(RolapSchemaLoader.java:1051)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> mondrian.rolap.RolapSchemaLoader.validatePhysicalSchema(RolapSchemaLoader.java:715)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>
>> >>>>
>> >>
>> mondrian.rolap.RolapSchemaLoader.loadStage2(RolapSchemaLoader.java:376)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>
>> >>>>
>> >>
>> mondrian.rolap.RolapSchemaLoader.loadStage1(RolapSchemaLoader.java:336)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>
>> >>>>
>> >>
>> mondrian.rolap.RolapSchemaLoader.loadStage0(RolapSchemaLoader.java:272)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> mondrian.rolap.RolapSchemaLoader.createSchema(RolapSchemaLoader.java:4303)*
>> >>>>>>>> * 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>(MondrianOlap4jConnection.java:153)*
>> >>>>>>>> * at
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>> mondrian.olap4j.FactoryJdbc4Plus$AbstractConnection.<init>(FactoryJdbc4Plus.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-dev/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
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >>
>>
>>

Re: Modrian with Kylin

Posted by divye sheth <di...@gmail.com>.
Thanks Sebastian, I am using Mondrian 4 but not the branch you mentioned. I
have checked out the branch and will be building the mondrian jar, the
build.sh script does not make the jar. Will checkout the new kylin branch
and build again. Just for my info, what caused this issue?

Thank!
Divye Sheth
On Jun 8, 2015 20:25, "Sébastien Jelsch" <sj...@inovex.de> wrote:

> I found the reason for this issue (
> https://issues.apache.org/jira/browse/KYLIN-819 ) and fixed it (
> https://github.com/apache/incubator-kylin/pull/9/files ).
>
> Best Regards,
> Sébastien Jelsch
>
>
>
> > Am 22.05.2015 um 18:33 schrieb Luke Han <lu...@gmail.com>:
> >
> > Please handle this part to Shanghai team, I will put this story in v0.7.2
> > (after successful release v0.7.1).
> >
> > Thanks.
> >
> >
> > Best Regards!
> > ---------------------
> >
> > Luke Han
> >
> > 2015-05-23 0:25 GMT+08:00 divye sheth <di...@gmail.com>:
> >
> >> Will wait for the core committers. In the meantime might as well test
> kylin
> >> with 0.9.2.
> >>
> >> Thanks!
> >> On May 22, 2015 21:52, "Julian Hyde" <jh...@apache.org> wrote:
> >>
> >>> Calcite 0.9.2 -> 1.0 is a tricky upgrade. I think you should leave it
> to
> >>> the core committers.
> >>>
> >>> I wouldn't even be sure that the upgrade from 0.9.1 to 0.9.2 worked
> until
> >>> the tests had passed.
> >>>
> >>> On Fri, May 22, 2015 at 9:11 AM, divye sheth <di...@gmail.com>
> >> wrote:
> >>>
> >>>> The 0.9.2 release builds fine with Kylin (just built kylin have not
> >>>> tested). With the Calcite 1.0 release there have been significant
> >>>> class/package renaming and movement as well as some additional classes
> >>>> coming in. Currently I am trying to figure out AvaticaPrepareResult ->
> >>>> Meta.Signature
> >>>> I am trying my best here. Java is something that I am not that strong
> >>> with
> >>>> :-)
> >>>>
> >>>> Thanks
> >>>> Divye Sheth
> >>>> On May 22, 2015 21:12, "Julian Hyde" <jh...@apache.org> wrote:
> >>>>
> >>>>> There are significant API changes between Calcite 0.9 and 1.0. Read
> >> the
> >>>> 1.0
> >>>>> release notes
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> https://github.com/apache/incubator-calcite/blob/branch-1.3/doc/history.md#100-incubating--2015-01-31
> >>>>> ,
> >>>>> and use the API mapping
> >>>>>
> >> https://issues.apache.org/jira/secure/attachment/12681620/mapping.txt
> >>> if
> >>>>> you need to. Consider upgrading to 0.9.2 (the last release with the
> >> old
> >>>>> API) and getting that working before moving to the renamed API.
> >>>>>
> >>>>> I've logged https://issues.apache.org/jira/browse/KYLIN-780 to track
> >>>> this.
> >>>>>
> >>>>>
> >>>>> On Thu, May 21, 2015 at 9:51 PM, divye sheth <di...@gmail.com>
> >>>> wrote:
> >>>>>
> >>>>>> Thanks Julian, will try porting optiq 0.9 to calcite 1.0. Will
> >> commit
> >>>> if
> >>>>>> successfull.
> >>>>>>
> >>>>>> Thanks
> >>>>>> Divye Sheth
> >>>>>> On May 21, 2015 22:18, "Julian Hyde" <jh...@apache.org> wrote:
> >>>>>>
> >>>>>>> It seems that Mondrian is trying to access a string column as if
> >> it
> >>>>> were
> >>>>>> a
> >>>>>>> long. Maybe you declared the column of the wrong type in your
> >>>> Mondrian
> >>>>>>> schema file? Or maybe Kylin is not reporting the type accurately.
> >>>>>>>
> >>>>>>> The JDBC driver code that is failing to convert (
> >>>>>>> *net.hydromatic.optiq.runtime.AbstractCursor*) is in Optiq, now
> >>>> called
> >>>>>>> Calcite. Later versions of Calcite are more permissive about
> >>>>> conversions
> >>>>>> so
> >>>>>>> if Kylin upgraded to a more recent version of Calcite that would
> >>>>> probably
> >>>>>>> improve things.
> >>>>>>>
> >>>>>>> On Wed, May 20, 2015 at 2:47 AM, divye sheth <
> >> divs.sheth@gmail.com
> >>>>
> >>>>>> wrote:
> >>>>>>>
> >>>>>>>> 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(AbstractCursor.java:243)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> net.hydromatic.optiq.runtime.AbstractCursor$AccessorImpl.getInt(AbstractCursor.java:239)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> net.hydromatic.avatica.AvaticaResultSet.getInt(AvaticaResultSet.java:220)*
> >>>>>>>> * 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(RolapSchema.java:1519)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> mondrian.rolap.RolapSchema$PhysTable.ensurePopulated(RolapSchema.java:1729)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> mondrian.rolap.RolapSchemaLoader.registerTable(RolapSchemaLoader.java:1051)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> mondrian.rolap.RolapSchemaLoader.validatePhysicalSchema(RolapSchemaLoader.java:715)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>
> >>>>
> >> mondrian.rolap.RolapSchemaLoader.loadStage2(RolapSchemaLoader.java:376)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>
> >>>>
> >> mondrian.rolap.RolapSchemaLoader.loadStage1(RolapSchemaLoader.java:336)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>
> >>>>
> >> mondrian.rolap.RolapSchemaLoader.loadStage0(RolapSchemaLoader.java:272)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> mondrian.rolap.RolapSchemaLoader.createSchema(RolapSchemaLoader.java:4303)*
> >>>>>>>> * 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>(MondrianOlap4jConnection.java:153)*
> >>>>>>>> * at
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
> mondrian.olap4j.FactoryJdbc4Plus$AbstractConnection.<init>(FactoryJdbc4Plus.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-dev/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
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >>
>
>