Druid SQL FLOOR time function should support all the time units it shows in error messages

[sashidhar]

Affected Version

Druid version 0.15.0 (and probably all other previous versions)

Description

Run the below query

SELECT FLOOR(CURRENT_TIMESTAMP TO XYZ) from wikipedia limit 1;

It returns the following error message:

Unknown exception / Encountered "TO XYZ" at line 1, column 47. Was expecting one of: ")" ... "NOT" ... "IN" ... "<" ... "<=" ... ">" ... ">=" ... "=" ... "<>" ... "!=" ... "BETWEEN" ... "LIKE" ... "SIMILAR" ... "+" ... "-" ... "*" ... "/" ... "%" ... "||" ... "AND" ... "OR" ... "IS" ... "MEMBER" ... "SUBMULTISET" ... "CONTAINS" ... "OVERLAPS" ... "EQUALS" ... "PRECEDES" ... "SUCCEEDS" ... "IMMEDIATELY" ... "MULTISET" ... "[" ... "(" ... "TO" "MICROSECOND" ... "TO" "MILLISECOND" ... "TO" "SECOND" ... "TO" "MINUTE" ... "TO" "HOUR" ... "TO" "DAY" ... "TO" "DOW" ... "TO" "DOY" ... "TO" "ISODOW" ... "TO" "ISOYEAR" ... "TO" "WEEK" ... "TO" "MONTH" ... "TO" "QUARTER" ... "TO" "YEAR" ... "TO" "EPOCH" ... "TO" "DECADE" ... "TO" "CENTURY" ... "TO" "MILLENNIUM" ... / org.apache.calcite.sql.parser.SqlParseException

FLOOR function doesn't support these time units mentioned in the above error message - MICROSECOND, MILLISECOND, DOW, DOY, ISODOW, ISOYEAR, EPOCH, DECADE, CENTURY and MILLENNIUM

For example,

SELECT FLOOR(CURRENT_TIMESTAMP TO MICROSECOND) from wikipedia limit 1;

returns

Unknown exception / Cannot build plan for query: SELECT * FROM (SELECT FLOOR(CURRENT_TIMESTAMP TO MICROSECOND) from wikipedia limit 1) LIMIT 5000 / org.apache.druid.java.util.common.ISE

SELECT FLOOR(CURRENT_TIMESTAMP TO ISOYEAR) from wikipedia limit 1;

returns

Unknown exception / ISOYEAR / org.apache.calcite.sql.parser.SqlParseException

Found this while playing around with FLOOR function on the lines of #7935.

[stale]

This issue has been marked as stale due to 280 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.

[stale]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.