[jira] [Commented] (KYLIN-2812) Save to wrong database when loading Kafka Topic
[ https://issues.apache.org/jira/browse/KYLIN-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16185944#comment-16185944 ] Billy Liu commented on KYLIN-2812: -- Thanks Shaofengâs review. Now has renamed to timestampField. The change is back-compatible. All properties including tsColName will be included as before. > Save to wrong database when loading Kafka Topic > > > Key: KYLIN-2812 > URL: https://issues.apache.org/jira/browse/KYLIN-2812 > Project: Kylin > Issue Type: Bug >Reporter: Billy Liu >Assignee: Billy Liu >Priority: Minor > Fix For: v2.2.0 > > > When loading Kafka Topic, user could select the destination database name. > Currently, all topics are saved into DEFAULT database, which is not expected. > Here is a bug during reading create table parameter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (KYLIN-2812) Save to wrong database when loading Kafka Topic
[ https://issues.apache.org/jira/browse/KYLIN-2812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16178072#comment-16178072 ] Shaofeng SHI commented on KYLIN-2812: - hi "timestamp" is a single word, e.g: https://www.epochconverter.com/. The property of "parserTimeStampField" is confusing, suggest to use "timestampField" or similar. By the way, "tsColName=order_time" has been used in legacy cubes, is this change back-compatible with it? > Save to wrong database when loading Kafka Topic > > > Key: KYLIN-2812 > URL: https://issues.apache.org/jira/browse/KYLIN-2812 > Project: Kylin > Issue Type: Bug >Reporter: Billy Liu >Assignee: Billy Liu >Priority: Minor > Fix For: v2.2.0 > > > When loading Kafka Topic, user could select the destination database name. > Currently, all topics are saved into DEFAULT database, which is not expected. > Here is a bug during reading create table parameter. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
