I'm not sure on that, I don't have the environment :-); You can take a try,
or build a snapshot version from the master branch.

Best regards,

Shaofeng Shi 史少锋
Apache Kylin PMC
Email: [email protected]

Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
Join Kylin user mail group: [email protected]
Join Kylin dev mail group: [email protected]




Discovery <[email protected]> 于2020年5月22日周五 下午6:29写道:

> Hi Shaofeng,
>     Thanks for your quick reply, if I switch to use version 2.6.6, is it a
> similiar issue with HBase 2.0.x?
>
> Best Regards
> Discovery
>
>
>
> ------------------ 原始邮件 ------------------
> *发件人:* "ShaoFeng Shi"<[email protected]>;
> *发送时间:* 2020年5月22日(星期五) 晚上6:16
> *收件人:* "user"<[email protected]>;
> *主题:* Re: Start kylin3.0.2 failed due to Guava version mismatch with
> HBase 2.0.2
>
> Hello, such Guava conflict issue will be fixed in:
> https://issues.apache.org/jira/projects/KYLIN/issues/KYLIN-4394
>
> The target release is 3.1; There is a PR on this, I'm merging it; You can
> cherry-pick the patch if urgent.
>
> Best regards,
>
> Shaofeng Shi 史少锋
> Apache Kylin PMC
> Email: [email protected]
>
> Apache Kylin FAQ: https://kylin.apache.org/docs/gettingstarted/faq.html
> Join Kylin user mail group: [email protected]
> Join Kylin dev mail group: [email protected]
>
>
>
>
> Discovery <[email protected]> 于2020年5月22日周五 下午3:57写道:
>
>> Hi Kylin experts,
>>
>>            I am using latest Kylin 3.0.2 with Hadoop 3.1.1, HBase 2.0.2,
>> Spark 2.3.2, Hive 3.1.0, But I run into below issue when running "kylin.sh
>> start", I check the version Kylin uses 14.0 and HBase uses 28.0-jre
>> version. How can I get rid of this issue? Thanks in advance!
>>
>> 2020-05-22 15:34:16,520 INFO  [main] common.KylinConfig:150 : Initialized
>> a new KylinConfig from getInstanceFromEnv : 1496355635
>> 2020-05-22 15:34:16,591 INFO  [main] persistence.ResourceStore:90 : Using
>> metadata url kylin_metadata@hbase for resource store
>> Exception in thread "main" java.lang.IllegalArgumentException: Failed to
>> find metadata store by url: kylin_metadata@hbase
>> at
>> org.apache.kylin.common.persistence.ResourceStore.createResourceStore(ResourceStore.java:101)
>> at
>> org.apache.kylin.common.persistence.ResourceStore.getStore(ResourceStore.java:113)
>> at
>> org.apache.kylin.rest.service.AclTableMigrationTool.checkIfNeedMigrate(AclTableMigrationTool.java:99)
>> at
>> org.apache.kylin.tool.AclTableMigrationCLI.main(AclTableMigrationCLI.java:43)
>> Caused by: java.lang.reflect.InvocationTargetException
>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>> at
>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>> at
>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>> at
>> org.apache.kylin.common.persistence.ResourceStore.createResourceStore(ResourceStore.java:94)
>> ... 3 more
>> Caused by: java.lang.NoSuchMethodError:
>> com.google.common.base.Preconditions.checkArgument(ZLjava/lang/String;Ljava/lang/Object;)V
>> at org.apache.hadoop.conf.Configuration.set(Configuration.java:1358)
>> at org.apache.hadoop.conf.Configuration.set(Configuration.java:1339)
>> at
>> org.apache.kylin.common.util.HadoopUtil.healSickConfig(HadoopUtil.java:74)
>> at
>> org.apache.kylin.common.util.HadoopUtil.getCurrentConfiguration(HadoopUtil.java:60)
>> at
>> org.apache.kylin.storage.hbase.HBaseConnection.newHBaseConfiguration(HBaseConnection.java:170)
>> at
>> org.apache.kylin.storage.hbase.HBaseConnection.get(HBaseConnection.java:259)
>> at
>> org.apache.kylin.storage.hbase.HBaseResourceStore.getConnection(HBaseResourceStore.java:95)
>> at
>> org.apache.kylin.storage.hbase.HBaseResourceStore.createHTableIfNeeded(HBaseResourceStore.java:114)
>> at
>> org.apache.kylin.storage.hbase.HBaseResourceStore.<init>(HBaseResourceStore.java:88)
>> ... 8 more
>> 2020-05-22 15:34:16,903 INFO  [close-hbase-conn]
>> hbase.HBaseConnection:138 : Closing HBase connections...
>> ERROR: Unknown error. Please check full log.
>>
>> Best Regards
>> Discovery
>>
>

Reply via email to