Hi hubert:
Thanks to @youcheng.zhang (JIRA) who has fixed this bug. You can
cherry-pick this
commit(https://github.com/apache/kylin/commit/b4dace4db8304a53082265e614384132316801bb)
now or wait for
the next release.
Best Regards
Rongchuan.Jin
在 2019/1/16 下午6:15，“Rongchuan Jin”
Hi hubert:
I don’t think root cause is conflict between pushdown property.
Best Regards
Rongchuan.Jin
在 2019/1/16 下午5:50，“hubert stefani” 写入:
Ok. I will create the JIRA in a few minutes. Any chance there is a
conflict in the configuration with the kylin.query.pushdown.jdbc.
Ok. I will create the JIRA in a few minutes. Any chance there is a conflict in
the configuration with the kylin.query.pushdown.jdbc. properties ?
Le mercredi 16 janvier 2019 à 10:46:59 UTC+1, Rongchuan Jin
a écrit :
Hi hubert:
Your configuration seems okay. I reproduced it in my
Hi hubert:
Your configuration seems okay. I reproduced it in my environment, it seems
like a bug within ClassLoader. Welcome to create a JIRA ticket.
Best Regards
Rongchuan.Jin
在 2019/1/16 下午5:36，“hubert stefani” 写入:
Please find hereunder the kylin properties lines related to mysql
Please find hereunder the kylin properties lines related to mysql jdbc
connection: (it works properly through spark shell script)
# NOVAGEN -- CUSTOM CONFIGURATION FOR MYSQL AS SOURCE
kylin.source.jdbc.connection-url=jdbc:mysql://ip-172-31-36-94.eu-west-1.compute.internal:3306/decat
Hi Hubert,
Could you please provide your kylin.properties with prefix
“kylin.source.jdbc ” or just show your project configurations. I think it’s
easier to find the root cause.
Best Regards
Rongchuan.Jin
在 2019/1/14 下午9:24，“hubert stefani” 写入:
Hi,
we are currently trying
Hi,
we are currently trying to test the KYLIN-3552 feature to rely directly on
Mysql for data source instead of Hive.
(we tried as much as possible to add correct info in kylin.properties, add
mysql jdbc drivers, create mysql.xml in ./conf/datasources ... as mentioned in
