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

ASF subversion and git services commented on KYLIN-3689:
--------------------------------------------------------

Commit 45fb6a2661a9ae92a5766ace97d8a6a51f188f7c in kylin's branch 
refs/heads/master from 贺红涛
[ https://gitbox.apache.org/repos/asf?p=kylin.git;h=45fb6a2 ]

KYLIN-3689 When the startTime is equal to the endTime in build request, the 
segment will build all data.


> When the startTime is equal to the endTime in build request, the segment will 
> build all data.
> ---------------------------------------------------------------------------------------------
>
>                 Key: KYLIN-3689
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3689
>             Project: Kylin
>          Issue Type: Bug
>          Components: Job Engine, Metadata, Query Engine
>    Affects Versions: v2.4.0, v2.5.0
>            Reporter: Hongtao He
>            Assignee: Shaofeng SHI
>            Priority: Major
>             Fix For: v2.5.2
>
>         Attachments: 
> 0001-fix-bug-When-the-startTime-is-equal-to-the-endTime-i.patch
>
>
> Hi all:
>   We  know that kylin's build job often runs late at night, so calling 
> kylin's restful API directly is a very common thing. In this scenario, if  
> the startTime is equal to the endTime,  something unexpected will happen. The 
>  job calculates all partition data, so the query result is wrong.
>   For example, when I send the following request to kylin.
> curl -X PUT -H "Authorization: Basic XXXXXXX" -H 'Content-Type: 
> application/json' -d '\{"startTime":'1541894400000', 
> "endTime":'1541894400000', "buildType":"BUILD"}' 
> [http://xxxxxx:xxxx/kylin/api/cubes/cube_name/build|http://xxxxxxxxxx/]
> then, the job will calculate all partition data. I find the backend interface 
> of build lacks checksum data range, and the sql of generating the flat table 
> is wrong. 
>   I try to fix this bug, and the patch  is in the attachment.
>  



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

Reply via email to