The partitioning is by java Date type (in its long form) in the backend. So timestamp support in this sense was always there. The GUI only allows date, however, is because all cases we've done so far didn't require a finer time granularity. Will expose more options.
On Wed, Mar 11, 2015 at 12:34 PM, Luke Han <[email protected]> wrote: > Supporting timestamp is one enhancement should to be done, even should > considering String type with given date format. > > Here's JIRA for tracking: https://issues.apache.org/jira/browse/KYLIN-633 > > Thanks. > > > Best Regards! > --------------------- > > Luke Han > > 2015-03-10 19:25 GMT-07:00 dong wang <[email protected]>: > > > As we know that from kylin 0.71, we must define a "date" column if we > want > > to have a partition column when designing a cube, of course, it's > > reasonable, however, it is not that flexible, is it possible that we can > > aslo support "timestamp" type since "timestamp" are much more flexible > than > > "date",and which can be recognized in many other database and much easier > > to be converted to other date type, especially for "impala", "impala" > only > > supports "timestamp" > > >
