[jira] [Commented] (KYLIN-5016) Avoid potential NPE issue in RDBMS Pushdown case
[
https://issues.apache.org/jira/browse/KYLIN-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369199#comment-17369199
]
rongchuan.jin commented on KYLIN-5016:
--
*[Root Cause]*
I found SqlDialect.CALCITE may be null in my debug env, this may be the root
cause of above npe issue which also is empty dialect.
So I try to replace SqlDialect.CALCITE with
SqlDialect.DatabaseProduct.CALCITE.getDialect() which will be initialed for
sure. As SqlDialect.CALCITE is a static field in SqlDialect which might not be
initialize at that time.
> Avoid potential NPE issue in RDBMS Pushdown case
>
>
> Key: KYLIN-5016
> URL: https://issues.apache.org/jira/browse/KYLIN-5016
> Project: Kylin
> Issue Type: Improvement
> Components: RDBMS Source
>Affects Versions: v2.6.5, v3.1.2
>Reporter: rongchuan.jin
>Assignee: rongchuan.jin
>Priority: Minor
>
> When I use pushdown with RDBMS source, I encounter some error when convert
> sql which leads to pushdown failing.
> I find below stacktrace like
> {code:java}
> 2020-12-23 13:14:10,212 ERROR [Query a1bf28bb-de28-433e-ab96-28ce234a1a4a-76]
> conv.SqlConverter : Failed to default convert sql, will use the origin input:
> select 1 from `MOVIES_10M`.`DIM_MOVIES_10M` 2LIMIT 500
> 3java.lang.NullPointerException 4 at
> org.apache.calcite.sql.SqlCall.unparse(SqlCall.java:103) 5 at
> org.apache.calcite.sql.pretty.SqlPrettyWriter.format(SqlPrettyWriter.java:806)
> 6 at
> org.apache.kylin.sdk.datasource.framework.conv.SqlConverter.convertSql(SqlConverter.java:69)
> 7 at
> org.apache.kylin.sdk.datasource.framework.JdbcConnector.convertSql(JdbcConnector.java:91)
> 8 at
> org.apache.kylin.sdk.datasource.PushDownRunnerSDKImpl.executeQuery(PushDownRunnerSDKImpl.java:55)
> 9 at
> org.apache.kylin.query.util.PushDownUtil.tryPushDownQuery(PushDownUtil.java:173)
> 10 at
> org.apache.kylin.query.util.PushDownUtil.tryPushDownSelectQuery(PushDownUtil.java:103)
> 11 at
> org.apache.kylin.rest.service.QueryService.tryPushDownSelectQuery(QueryService.java:773)
> 12 at
> org.apache.kylin.rest.service.QueryService.pushDownQuery(QueryService.java:709)
> 13 at
> org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:700)
> 14 at
> org.apache.kylin.rest.service.QueryService.query(QueryService.java:231) 15 at
> org.apache.kylin.rest.service.QueryService.queryAndUpdateCache(QueryService.java:577)
> 16 at
> org.apache.kylin.rest.service.QueryService.queryWithCache(QueryService.java:512)
> 17 at
> org.apache.kylin.rest.service.QueryService.doQueryWithCache(QueryService.java:395){code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (KYLIN-5016) Avoid potential NPE issue in RDBMS Pushdown case
[
https://issues.apache.org/jira/browse/KYLIN-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17369199#comment-17369199
]
rongchuan.jin edited comment on KYLIN-5016 at 6/25/21, 2:45 AM:
*[Root Cause & Fix Design]*
I found SqlDialect.CALCITE may be null in my debug env, this may be the root
cause of above npe issue which also is empty dialect.
So I try to replace SqlDialect.CALCITE with
SqlDialect.DatabaseProduct.CALCITE.getDialect() which will be initialed for
sure. As SqlDialect.CALCITE is a static field in SqlDialect which might not be
initialize at that time.
was (Author: rongchuan.jin):
*[Root Cause]*
I found SqlDialect.CALCITE may be null in my debug env, this may be the root
cause of above npe issue which also is empty dialect.
So I try to replace SqlDialect.CALCITE with
SqlDialect.DatabaseProduct.CALCITE.getDialect() which will be initialed for
sure. As SqlDialect.CALCITE is a static field in SqlDialect which might not be
initialize at that time.
> Avoid potential NPE issue in RDBMS Pushdown case
>
>
> Key: KYLIN-5016
> URL: https://issues.apache.org/jira/browse/KYLIN-5016
> Project: Kylin
> Issue Type: Improvement
> Components: RDBMS Source
>Affects Versions: v2.6.5, v3.1.2
>Reporter: rongchuan.jin
>Assignee: rongchuan.jin
>Priority: Minor
>
> When I use pushdown with RDBMS source, I encounter some error when convert
> sql which leads to pushdown failing.
> I find below stacktrace like
> {code:java}
> 2020-12-23 13:14:10,212 ERROR [Query a1bf28bb-de28-433e-ab96-28ce234a1a4a-76]
> conv.SqlConverter : Failed to default convert sql, will use the origin input:
> select 1 from `MOVIES_10M`.`DIM_MOVIES_10M` 2LIMIT 500
> 3java.lang.NullPointerException 4 at
> org.apache.calcite.sql.SqlCall.unparse(SqlCall.java:103) 5 at
> org.apache.calcite.sql.pretty.SqlPrettyWriter.format(SqlPrettyWriter.java:806)
> 6 at
> org.apache.kylin.sdk.datasource.framework.conv.SqlConverter.convertSql(SqlConverter.java:69)
> 7 at
> org.apache.kylin.sdk.datasource.framework.JdbcConnector.convertSql(JdbcConnector.java:91)
> 8 at
> org.apache.kylin.sdk.datasource.PushDownRunnerSDKImpl.executeQuery(PushDownRunnerSDKImpl.java:55)
> 9 at
> org.apache.kylin.query.util.PushDownUtil.tryPushDownQuery(PushDownUtil.java:173)
> 10 at
> org.apache.kylin.query.util.PushDownUtil.tryPushDownSelectQuery(PushDownUtil.java:103)
> 11 at
> org.apache.kylin.rest.service.QueryService.tryPushDownSelectQuery(QueryService.java:773)
> 12 at
> org.apache.kylin.rest.service.QueryService.pushDownQuery(QueryService.java:709)
> 13 at
> org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:700)
> 14 at
> org.apache.kylin.rest.service.QueryService.query(QueryService.java:231) 15 at
> org.apache.kylin.rest.service.QueryService.queryAndUpdateCache(QueryService.java:577)
> 16 at
> org.apache.kylin.rest.service.QueryService.queryWithCache(QueryService.java:512)
> 17 at
> org.apache.kylin.rest.service.QueryService.doQueryWithCache(QueryService.java:395){code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (KYLIN-5016) Avoid potential NPE issue in RDBMS Pushdown case
[
https://issues.apache.org/jira/browse/KYLIN-5016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rongchuan.jin updated KYLIN-5016:
-
Description:
When I use pushdown with RDBMS source, I encounter some error when convert sql
which leads to pushdown failing.
I find below stacktrace like
{code:java}
2020-12-23 13:14:10,212 ERROR [Query a1bf28bb-de28-433e-ab96-28ce234a1a4a-76]
conv.SqlConverter : Failed to default convert sql, will use the origin input:
select 1 from `MOVIES_10M`.`DIM_MOVIES_10M` 2LIMIT 500
3java.lang.NullPointerException 4 at
org.apache.calcite.sql.SqlCall.unparse(SqlCall.java:103) 5 at
org.apache.calcite.sql.pretty.SqlPrettyWriter.format(SqlPrettyWriter.java:806)
6 at
org.apache.kylin.sdk.datasource.framework.conv.SqlConverter.convertSql(SqlConverter.java:69)
7 at
org.apache.kylin.sdk.datasource.framework.JdbcConnector.convertSql(JdbcConnector.java:91)
8 at
org.apache.kylin.sdk.datasource.PushDownRunnerSDKImpl.executeQuery(PushDownRunnerSDKImpl.java:55)
9 at
org.apache.kylin.query.util.PushDownUtil.tryPushDownQuery(PushDownUtil.java:173)
10 at
org.apache.kylin.query.util.PushDownUtil.tryPushDownSelectQuery(PushDownUtil.java:103)
11 at
org.apache.kylin.rest.service.QueryService.tryPushDownSelectQuery(QueryService.java:773)
12 at
org.apache.kylin.rest.service.QueryService.pushDownQuery(QueryService.java:709)
13 at
org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:700)
14 at org.apache.kylin.rest.service.QueryService.query(QueryService.java:231)
15 at
org.apache.kylin.rest.service.QueryService.queryAndUpdateCache(QueryService.java:577)
16 at
org.apache.kylin.rest.service.QueryService.queryWithCache(QueryService.java:512)
17 at
org.apache.kylin.rest.service.QueryService.doQueryWithCache(QueryService.java:395){code}
was:
When I use pushdown with RDBMS source, I encounter some error when convert sql
which leads to pushdown failing.
I find below stacktrace like
`2020-12-23 13:14:10,212 ERROR [Query a1bf28bb-de28-433e-ab96-28ce234a1a4a-76]
conv.SqlConverter : Failed to default convert sql, will use the origin input:
select 1 from `MOVIES_10M`.`DIM_MOVIES_10M` 2LIMIT 500
3java.lang.NullPointerException 4 at
org.apache.calcite.sql.SqlCall.unparse(SqlCall.java:103) 5 at
org.apache.calcite.sql.pretty.SqlPrettyWriter.format(SqlPrettyWriter.java:806)
6 at
org.apache.kylin.sdk.datasource.framework.conv.SqlConverter.convertSql(SqlConverter.java:69)
7 at
org.apache.kylin.sdk.datasource.framework.JdbcConnector.convertSql(JdbcConnector.java:91)
8 at
org.apache.kylin.sdk.datasource.PushDownRunnerSDKImpl.executeQuery(PushDownRunnerSDKImpl.java:55)
9 at
org.apache.kylin.query.util.PushDownUtil.tryPushDownQuery(PushDownUtil.java:173)
10 at
org.apache.kylin.query.util.PushDownUtil.tryPushDownSelectQuery(PushDownUtil.java:103)
11 at
org.apache.kylin.rest.service.QueryService.tryPushDownSelectQuery(QueryService.java:773)
12 at
org.apache.kylin.rest.service.QueryService.pushDownQuery(QueryService.java:709)
13 at
org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:700)
14 at org.apache.kylin.rest.service.QueryService.query(QueryService.java:231)
15 at
org.apache.kylin.rest.service.QueryService.queryAndUpdateCache(QueryService.java:577)
16 at
org.apache.kylin.rest.service.QueryService.queryWithCache(QueryService.java:512)
17 at
org.apache.kylin.rest.service.QueryService.doQueryWithCache(QueryService.java:395)`
> Avoid potential NPE issue in RDBMS Pushdown case
>
>
> Key: KYLIN-5016
> URL: https://issues.apache.org/jira/browse/KYLIN-5016
> Project: Kylin
> Issue Type: Improvement
> Components: RDBMS Source
>Affects Versions: v2.6.5, v3.1.2
>Reporter: rongchuan.jin
>Assignee: rongchuan.jin
>Priority: Minor
>
> When I use pushdown with RDBMS source, I encounter some error when convert
> sql which leads to pushdown failing.
> I find below stacktrace like
> {code:java}
> 2020-12-23 13:14:10,212 ERROR [Query a1bf28bb-de28-433e-ab96-28ce234a1a4a-76]
> conv.SqlConverter : Failed to default convert sql, will use the origin input:
> select 1 from `MOVIES_10M`.`DIM_MOVIES_10M` 2LIMIT 500
> 3java.lang.NullPointerException 4 at
> org.apache.calcite.sql.SqlCall.unparse(SqlCall.java:103) 5 at
> org.apache.calcite.sql.pretty.SqlPrettyWriter.format(SqlPrettyWriter.java:806)
> 6 at
> org.apache.kylin.sdk.datasource.framework.conv.SqlConverter.convertSql(SqlConverter.java:69)
> 7 at
> org.apache.kylin.sdk.datasource.framework.JdbcConnector.convertSql(JdbcConnector.java:91)
> 8 at
> org.apache.kylin.sdk.datasource.PushDownRunnerSDKImpl.executeQuery(PushDownRunnerSDKImpl.java:55)
> 9 at
> org.apache.kylin.query.util.PushDownUtil.tryPushDownQuery(PushDownUtil.java:173)
> 10 at
>
[jira] [Created] (KYLIN-5016) Avoid potential NPE issue in RDBMS Pushdown case
rongchuan.jin created KYLIN-5016: Summary: Avoid potential NPE issue in RDBMS Pushdown case Key: KYLIN-5016 URL: https://issues.apache.org/jira/browse/KYLIN-5016 Project: Kylin Issue Type: Improvement Components: RDBMS Source Affects Versions: v3.1.2, v2.6.5 Reporter: rongchuan.jin Assignee: rongchuan.jin When I use pushdown with RDBMS source, I encounter some error when convert sql which leads to pushdown failing. I find below stacktrace like `2020-12-23 13:14:10,212 ERROR [Query a1bf28bb-de28-433e-ab96-28ce234a1a4a-76] conv.SqlConverter : Failed to default convert sql, will use the origin input: select 1 from `MOVIES_10M`.`DIM_MOVIES_10M` 2LIMIT 500 3java.lang.NullPointerException 4 at org.apache.calcite.sql.SqlCall.unparse(SqlCall.java:103) 5 at org.apache.calcite.sql.pretty.SqlPrettyWriter.format(SqlPrettyWriter.java:806) 6 at org.apache.kylin.sdk.datasource.framework.conv.SqlConverter.convertSql(SqlConverter.java:69) 7 at org.apache.kylin.sdk.datasource.framework.JdbcConnector.convertSql(JdbcConnector.java:91) 8 at org.apache.kylin.sdk.datasource.PushDownRunnerSDKImpl.executeQuery(PushDownRunnerSDKImpl.java:55) 9 at org.apache.kylin.query.util.PushDownUtil.tryPushDownQuery(PushDownUtil.java:173) 10 at org.apache.kylin.query.util.PushDownUtil.tryPushDownSelectQuery(PushDownUtil.java:103) 11 at org.apache.kylin.rest.service.QueryService.tryPushDownSelectQuery(QueryService.java:773) 12 at org.apache.kylin.rest.service.QueryService.pushDownQuery(QueryService.java:709) 13 at org.apache.kylin.rest.service.QueryService.queryWithSqlMassage(QueryService.java:700) 14 at org.apache.kylin.rest.service.QueryService.query(QueryService.java:231) 15 at org.apache.kylin.rest.service.QueryService.queryAndUpdateCache(QueryService.java:577) 16 at org.apache.kylin.rest.service.QueryService.queryWithCache(QueryService.java:512) 17 at org.apache.kylin.rest.service.QueryService.doQueryWithCache(QueryService.java:395)` -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4365) RDBMS pushdown failed with with clause
rongchuan.jin created KYLIN-4365: Summary: RDBMS pushdown failed with with clause Key: KYLIN-4365 URL: https://issues.apache.org/jira/browse/KYLIN-4365 Project: Kylin Issue Type: Bug Components: Query Engine, RDBMS Source Affects Versions: all Reporter: rongchuan.jin Assignee: rongchuan.jin Fix For: v3.1.0 When use pushdown for RDBMS, I query with following sql: `with tmp as (select id from a),tmp2 as (select * from b) select * from tmp,tmp2 where tmp.id = tmp2.id` it will cause exception like 'table tmp not exists'. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (KYLIN-4364) Limit varchar length to DefaultVarcharPrecison in RDBMS Source
rongchuan.jin created KYLIN-4364: Summary: Limit varchar length to DefaultVarcharPrecison in RDBMS Source Key: KYLIN-4364 URL: https://issues.apache.org/jira/browse/KYLIN-4364 Project: Kylin Issue Type: Improvement Components: RDBMS Source Affects Versions: all Reporter: rongchuan.jin Assignee: rongchuan.jin Fix For: v3.1.0 We should limit varchar length from RDBMS source in case causing OOM error in later building steps. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (KYLIN-3779) JDBC sources with Case sensitive behaviour
[ https://issues.apache.org/jira/browse/KYLIN-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747765#comment-16747765 ] rongchuan.jin commented on KYLIN-3779: -- That's a pity it could not be kept in original case since there are many places to upperCase column in the early kylin version.That's why we have the property sql.case-sensitive and metadata.enable-cache to solve this problem.Please refer to this doc [http://kylin.apache.org/blog/2019/01/16/introduce-data-source-sdk-v2.6.0/] > JDBC sources with Case sensitive behaviour > -- > > Key: KYLIN-3779 > URL: https://issues.apache.org/jira/browse/KYLIN-3779 > Project: Kylin > Issue Type: Bug > Components: RDBMS Source >Affects Versions: v2.6.0 >Reporter: Hubert STEFANI >Priority: Major > > When using a Mysql instance with names (database, tables, columns) in lower > case, Kylin converts names to upper case in metadata tables. > Hence, when trying to build the cube, the upper case names are used (through > SQOOP) to load data and the sqoop step fails. > could the names be kept in original case ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (KYLIN-3779) JDBC sources with Case sensitive behaviour
[ https://issues.apache.org/jira/browse/KYLIN-3779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16747769#comment-16747769 ] rongchuan.jin commented on KYLIN-3779: -- [~hstefani] You can change the mysql.xml configuration in Kylin (e.g. set sql.case-sensitive property to false) rather than change your MySQL system. Please refer to https://issues.apache.org/jira/browse/KYLIN-3749 to override your configuration. > JDBC sources with Case sensitive behaviour > -- > > Key: KYLIN-3779 > URL: https://issues.apache.org/jira/browse/KYLIN-3779 > Project: Kylin > Issue Type: Bug > Components: RDBMS Source >Affects Versions: v2.6.0 >Reporter: Hubert STEFANI >Priority: Major > > When using a Mysql instance with names (database, tables, columns) in lower > case, Kylin converts names to upper case in metadata tables. > Hence, when trying to build the cube, the upper case names are used (through > SQOOP) to load data and the sqoop step fails. > could the names be kept in original case ? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3749) Add configuration to override xml for RDBMS
rongchuan.jin created KYLIN-3749:
Summary: Add configuration to override xml for RDBMS
Key: KYLIN-3749
URL: https://issues.apache.org/jira/browse/KYLIN-3749
Project: Kylin
Issue Type: Improvement
Components: RDBMS Source
Affects Versions: v2.6.0
Environment: MacOSX,JDK1.8
Reporter: rongchuan.jin
Fix For: v2.6.0
Currently, Kylin package xml file for RDBMS, if I want to change the
configuration for MySQL datasource like change some function mapping relation,
the only way is to change the source code and repackage it.Which is annoying.
Inspired by kylin.properties.override , I find it easy to solve this problem.
How to do this:
1. ${KYLIN_HOME}/conf ,make a new directory named datasource
2. copy mysql.xml(for example) to ${KYLIN_HOME}/conf/datasource, change
its name to mysql.xml.override.Thus you can modify that xml file whatever you
want.
3. Restart Kylin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KYLIN-3749) Add configuration to override xml for RDBMS
[
https://issues.apache.org/jira/browse/KYLIN-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rongchuan.jin reassigned KYLIN-3749:
Assignee: rongchuan.jin
> Add configuration to override xml for RDBMS
> ---
>
> Key: KYLIN-3749
> URL: https://issues.apache.org/jira/browse/KYLIN-3749
> Project: Kylin
> Issue Type: Improvement
> Components: RDBMS Source
>Affects Versions: v2.6.0
> Environment: MacOSX,JDK1.8
>Reporter: rongchuan.jin
>Assignee: rongchuan.jin
>Priority: Major
> Fix For: v2.6.0
>
>
> Currently, Kylin package xml file for RDBMS, if I want to change the
> configuration for MySQL datasource like change some function mapping
> relation, the only way is to change the source code and repackage it.Which is
> annoying.
> Inspired by kylin.properties.override , I find it easy to solve this
> problem.
> How to do this:
> 1. ${KYLIN_HOME}/conf ,make a new directory named datasource
> 2. copy mysql.xml(for example) to ${KYLIN_HOME}/conf/datasource, change
> its name to mysql.xml.override.Thus you can modify that xml file whatever you
> want.
> 3. Restart Kylin.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (KYLIN-3737) Refactor cache part for RDBMS
[ https://issues.apache.org/jira/browse/KYLIN-3737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rongchuan.jin reassigned KYLIN-3737: Assignee: rongchuan.jin > Refactor cache part for RDBMS > - > > Key: KYLIN-3737 > URL: https://issues.apache.org/jira/browse/KYLIN-3737 > Project: Kylin > Issue Type: Improvement > Components: RDBMS Source >Affects Versions: v2.6.0 > Environment: MacOSx,JDK1.8 >Reporter: rongchuan.jin >Assignee: rongchuan.jin >Priority: Major > Fix For: v2.6.0 > > > Currently, Kylin cache part for RDBMS has poor performance while load many > tables with sql-case-sensitive,it will take much time to load > database,table,column identifier to cache in order to fix sql-case-sensitive > problem for RDBMS.I found it has space to imporve .So I'd like to contribute > a patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3737) Refactor cache part for RDBMS
rongchuan.jin created KYLIN-3737: Summary: Refactor cache part for RDBMS Key: KYLIN-3737 URL: https://issues.apache.org/jira/browse/KYLIN-3737 Project: Kylin Issue Type: Improvement Components: RDBMS Source Affects Versions: v2.6.0 Environment: MacOSx,JDK1.8 Reporter: rongchuan.jin Fix For: v2.6.0 Currently, Kylin cache part for RDBMS has poor performance while load many tables with sql-case-sensitive,it will take much time to load database,table,column identifier to cache in order to fix sql-case-sensitive problem for RDBMS.I found it has space to imporve .So I'd like to contribute a patch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3721) Failed to get source table when write the wrong password at the first time
rongchuan.jin created KYLIN-3721: Summary: Failed to get source table when write the wrong password at the first time Key: KYLIN-3721 URL: https://issues.apache.org/jira/browse/KYLIN-3721 Project: Kylin Issue Type: Bug Components: RDBMS Source Affects Versions: v2.6.0 Environment: MacOSX,JDK1.8 Reporter: rongchuan.jin Fix For: v2.6.0 When I write RDBMS configuration,I has written the wrong password the first time.It can not load tables. Then I change the right password in configuration, it can not load table until I restart Kylin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-3721) Failed to get source table when write the wrong password at the first time
[ https://issues.apache.org/jira/browse/KYLIN-3721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rongchuan.jin reassigned KYLIN-3721: Assignee: rongchuan.jin > Failed to get source table when write the wrong password at the first time > --- > > Key: KYLIN-3721 > URL: https://issues.apache.org/jira/browse/KYLIN-3721 > Project: Kylin > Issue Type: Bug > Components: RDBMS Source >Affects Versions: v2.6.0 > Environment: MacOSX,JDK1.8 >Reporter: rongchuan.jin >Assignee: rongchuan.jin >Priority: Minor > Fix For: v2.6.0 > > > When I write RDBMS configuration,I has written the wrong password the first > time.It can not load tables. > Then I change the right password in configuration, it can not load table > until I restart Kylin. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3707) Add configuration for setting isolation-level for sqoop
rongchuan.jin created KYLIN-3707: Summary: Add configuration for setting isolation-level for sqoop Key: KYLIN-3707 URL: https://issues.apache.org/jira/browse/KYLIN-3707 Project: Kylin Issue Type: Improvement Components: RDBMS Source Environment: MacOSX JDK1.8 Reporter: rongchuan.jin When use RDBMS as datasource,we use Apache Sqoop to import data from RDBMS to HDFS.Sqoop use read_commited isolation-level by default,while some RDBMS does not support read_commited level,so need to add a configuration to fix it. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-3663) Failed to delete project when project has more than one table
[
https://issues.apache.org/jira/browse/KYLIN-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
rongchuan.jin reassigned KYLIN-3663:
Assignee: rongchuan.jin
> Failed to delete project when project has more than one table
> -
>
> Key: KYLIN-3663
> URL: https://issues.apache.org/jira/browse/KYLIN-3663
> Project: Kylin
> Issue Type: Bug
> Components: Metadata
>Affects Versions: v2.5.0
> Environment: MacOSX,JDK1.8+
>Reporter: rongchuan.jin
>Assignee: rongchuan.jin
>Priority: Minor
> Fix For: v2.6.0
>
>
> When I drop a project with more than one table.(When there is only one
> table,it works well)
> It comes out an error:
> {code:java}
> org.apache.kylin.rest.exception.InternalErrorException: Failed to delete
> project. Caused by: null
> at
> org.apache.kylin.rest.controller.ProjectController.deleteProject(ProjectController.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205)
> at
> org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:133)
> at
> org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:97)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:827)
> at
> org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:738)
> at
> org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:967)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:901)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
> at
> org.springframework.web.servlet.FrameworkServlet.doDelete(FrameworkServlet.java:894)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:656)
> at
> org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:111)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:170)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
> at
> org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:158)
> at
> org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
> at
>
[jira] [Created] (KYLIN-3663) Failed to delete project when project has more than one table
rongchuan.jin created KYLIN-3663:
Summary: Failed to delete project when project has more than one
table
Key: KYLIN-3663
URL: https://issues.apache.org/jira/browse/KYLIN-3663
Project: Kylin
Issue Type: Bug
Components: Metadata
Affects Versions: v2.5.0
Environment: MacOSX,JDK1.8+
Reporter: rongchuan.jin
Fix For: v2.6.0
When I drop a project with more than one table.(When there is only one table,it
works well)
It comes out an error:
{code:java}
org.apache.kylin.rest.exception.InternalErrorException: Failed to delete
project. Caused by: null
at
org.apache.kylin.rest.controller.ProjectController.deleteProject(ProjectController.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205)
at
org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:133)
at
org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:97)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:827)
at
org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:738)
at
org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:967)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:901)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
at
org.springframework.web.servlet.FrameworkServlet.doDelete(FrameworkServlet.java:894)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:656)
at
org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:317)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:127)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:91)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:114)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.session.SessionManagementFilter.doFilter(SessionManagementFilter.java:137)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.authentication.AnonymousAuthenticationFilter.doFilter(AnonymousAuthenticationFilter.java:111)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter.doFilter(SecurityContextHolderAwareRequestFilter.java:170)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.savedrequest.RequestCacheAwareFilter.doFilter(RequestCacheAwareFilter.java:63)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.authentication.www.BasicAuthenticationFilter.doFilterInternal(BasicAuthenticationFilter.java:158)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
org.springframework.security.web.authentication.AbstractAuthenticationProcessingFilter.doFilter(AbstractAuthenticationProcessingFilter.java:200)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:331)
at
[jira] [Assigned] (KYLIN-3645) Kylin does not clean table metadata when drop project(Kafka Source)
[ https://issues.apache.org/jira/browse/KYLIN-3645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rongchuan.jin reassigned KYLIN-3645: Assignee: rongchuan.jin > Kylin does not clean table metadata when drop project(Kafka Source) > --- > > Key: KYLIN-3645 > URL: https://issues.apache.org/jira/browse/KYLIN-3645 > Project: Kylin > Issue Type: Bug > Components: Metadata, Streaming >Affects Versions: v2.4.1 > Environment: jdk1.8 > MacOS >Reporter: rongchuan.jin >Assignee: rongchuan.jin >Priority: Minor > Fix For: v2.5.1 > > > When I use Kafka streaming,there is a bug. My steps: > 1.Create a project named p1 > 2.Import a kafka table named DEFAULT.T1 > 3.drop project p1 > 4.create project p2 > 5.Import a kafka table named DEFAULT.T1 > It comes out an error: > The Streaming Config DEFAULT.T1 already exists. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3645) Kylin does not clean table metadata when drop project(Kafka Source)
rongchuan.jin created KYLIN-3645: Summary: Kylin does not clean table metadata when drop project(Kafka Source) Key: KYLIN-3645 URL: https://issues.apache.org/jira/browse/KYLIN-3645 Project: Kylin Issue Type: Bug Components: Metadata, Streaming Affects Versions: v2.4.1 Environment: jdk1.8 MacOS Reporter: rongchuan.jin Fix For: v2.5.1 When I use Kafka streaming,there is a bug. My steps: 1.Create a project named p1 2.Import a kafka table named DEFAULT.T1 3.drop project p1 4.create project p2 5.Import a kafka table named DEFAULT.T1 It comes out an error: The Streaming Config DEFAULT.T1 already exists. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (KYLIN-3471) Merge dictionary and statistics on yarn
[ https://issues.apache.org/jira/browse/KYLIN-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] rongchuan.jin reassigned KYLIN-3471: Assignee: rongchuan.jin (was: Chao Long) > Merge dictionary and statistics on yarn > --- > > Key: KYLIN-3471 > URL: https://issues.apache.org/jira/browse/KYLIN-3471 > Project: Kylin > Issue Type: Improvement > Components: Spark Engine >Reporter: Chao Long >Assignee: rongchuan.jin >Priority: Major > > Currently, merge dictionary and statistics step is in kylin`s jvm, which > causes a great burden on kylin. > we should move this step on yarn. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (KYLIN-3485) Make unloading table more flexible
rongchuan.jin created KYLIN-3485: Summary: Make unloading table more flexible Key: KYLIN-3485 URL: https://issues.apache.org/jira/browse/KYLIN-3485 Project: Kylin Issue Type: Improvement Components: RDBMS Source, REST Service, Streaming Reporter: rongchuan.jin Now Kylin use fixed code to unload streaming table , it only works with Kafka.If I want to use other streaming datasource to extend Kylin like Aliyun Loghub Service.It seems to be difficult. I would like contribute improvment to make unloading table more flexible. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
