[IMPALA-1503] Impala's date_sub and date_add functions are not automatically casting strings (in the correct format) to TIMESTAMP

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: Impala 2.0
• Component/s: Frontend
• Labels: planner timestamp
• Target Version: Product Backlog
• Assignee: Tim Armstrong
• Reporter: Alex Spencer
• Created: 21/Nov/14 14:55
• Updated: 24/Dec/20 00:02
• Resolved: 24/Dec/20 00:02

Description

To reproduce:

– This query works:
select date_sub(now(), interval 5 minutes);

– Get the string version of now and copy and place it below:
select now() as now;

– Paste in string and run this, Impala will error:
select date_sub('2014-11-21 15:49:05.312610000', interval 5 minutes);
– It should not error, but rather cast the string (as per the documentation:
http://www.cloudera.com/content/cloudera/en/documentation/cloudera-impala/latest/topics/impala_timestamp.html?scroll=timestamp
***The first argument can be a string, which is automatically cast to TIMESTAMP if it uses the recognized format, as described in TIMESTAMP Data Type.***

Issue Links

• duplicates: IMPALA-2268 implicit casting of string to timestamp for functions
• is duplicated by: IMPALA-2293 STRING operand should be coerced to TIMESTAMP in INTERVAL expression