[ 
https://issues.apache.org/jira/browse/KYLIN-3788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816279#comment-16816279
 ] 

ASF GitHub Bot commented on KYLIN-3788:
---------------------------------------

nichunen commented on pull request #599: KYLIN-3788 Modify the time conversion 
time zone of the kafka streaming access
URL: https://github.com/apache/kylin/pull/599
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


>  Kylin's internal time zone conversions are various and confusing
> -----------------------------------------------------------------
>
>                 Key: KYLIN-3788
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3788
>             Project: Kylin
>          Issue Type: Bug
>          Components: REST Service, Web 
>    Affects Versions: v2.5.2
>         Environment: Huawei FI
>            Reporter: zhao jintao
>            Assignee: zhao jintao
>            Priority: Major
>              Labels: TimeZone
>
> Hi, All team
> I found that Kylin has a variety of time zone conversions inside, which is 
> confusing. In some code, the time zone is "GMT" when converting time, and 
> some code uses the time zone specified in the configuration file 
> ("TimeZone.getTimeZone("GMT")" );
> For Example:
> in CubingJob.java, use TimeZone from configuration file:  
> format.setTimeZone(TimeZone.getTimeZone(
> config.getTimeZone())),
> but in TimeUtil.java, use GMT TimeZone:private static TimeZone gmt = 
> TimeZone.getTimeZone("GMT")
>  
> When inport data from Kafka Streaming Data,kylin generate "Data_Start", 
> "Hour_Start" uses the GMT time zone,  They are  some time zones later than 
> the real time. Why not use the time zone specified in the configuration file?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to