In a multitude of existing enterprise applications partitioning is done on a single column that fuse date and time into a single value (string, integer or big integer). Typical formats are YYYYMMDDHHMM or YYYYMMDDHHMMSS (e.g. 201801181621 and 20180118154734).
Such representation is human readable and provides natural sorting of the date/time values.
Lack of support for such date/time representation requires some ugly workarounds, like creating views that split date and time into separate columns or data copying into tables with different partitioning scheme, none of which is a particularly good solution.
More over, using views approach on Hive causes severe performance issues, due to inability of Hive optimizer correctly analyze filtering conditions auto-generated by Kylin during the flat table build step.