[ https://issues.apache.org/jira/browse/KYLIN-3665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Feng Liang updated KYLIN-3665: ------------------------------ Attachment: 0001-KYLIN-3665-Partition-time-column-may-never-be-added.patch > Partition time column may never be added > ---------------------------------------- > > Key: KYLIN-3665 > URL: https://issues.apache.org/jira/browse/KYLIN-3665 > Project: Kylin > Issue Type: Bug > Reporter: Chao Long > Assignee: Feng Liang > Priority: Major > Fix For: v2.6.0 > > Attachments: > 0001-KYLIN-3665-Partition-time-column-may-never-be-added.patch > > > The partition time column will never be added to the WHERE clause if the > partition date column is type of int or bigint and the date format is > "yyyyMMdd", "yyyyMMddHH", "yyyyMMddHHmm" or "yyyyMMddHHmmss". > Let’s say I have a fact table with two date partition column: day as the > format of integer (yyyyMMdd) and minute as the format of string (HHmm). I > have models created based on it and set the Partition Date Column to be “day” > with the format of yyyyMMdd and the Partition Time Column to be “minute” with > the format of HHmm. When I build the cube built on top of that model, I set > the Start Date to be 2018-11-01 00:00:00 and the End Date to be 2018-11-01 > 01:00:00. The building process is supposed to retrieve the data from the fact > table in the range of “day = 20181101 and minute>=’0000’ and minute<’0100’”. > However, it retrieves the data in the range of “WHERE 1=1 AND (DAY >= > 20181101 AND DAY < 20181101), so no data are actually retrieved. -- This message was sent by Atlassian JIRA (v7.6.3#76005)