we have opened a JIRA. And the reponse is as follows: millis format as partition column will not be support in short run. The reason is that millis format tends to come with large cardinality, which is not acceptable by kylin. As a workaround you may use hive view to map the millis format to 'yyyy-MM-dd' or 'yyyyMMdd' format. In my opinion, kylin can change the yyyy-MM-dd and yyyyMMdd to millis. and the cardinality is equal to the cardinality of 'yyyyMMdd' or yyyy-MM-dd.
------------------ ???????? ------------------ ??????: "Li Yang";<[email protected]>; ????????: 2016??5??19??(??????) ????4:49 ??????: "dev"<[email protected]>; ????: Re: Partition date column Please open a JIRA for the new feature. It should not be too difficult to support long millis as partition date column. On Tue, May 17, 2016 at 12:25 AM, ???? <[email protected]> wrote: > Hi all : > When we create the model, there is a property called partition date > column, and the format the web interface shows is yyyyMMdd or yyyy-MM-dd. > Can this partition date column be a timestamp like 1463406381 or > 1463415185143. > > > When we build the cube, there are two parameters called startTime and > endTime ,and the format the instruction shows is 1388563200000 for > 2014-1-1. Which column will be used to filter the data? If it use the > partition date column, is there any tranformation in the kylin?
