[jira] [Commented] (CALCITE-2358) Use null literal instead of empty string as argument for timestamp_parse Druid expression

["Nishant Bangarwa (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CALCITE-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16512292#comment-16512292 ] 

Nishant Bangarwa commented on CALCITE-2358:
-------------------------------------------

[~bslim] thanks for the PR. 
pushed to master via https://git-wip-us.apache.org/repos/asf?p=calcite.git;a=commit;h=4536000f2c4868b75f1000d61a8ac9ed0141fcfa

> Use null literal instead of empty string as argument for timestamp_parse Druid expression
> -----------------------------------------------------------------------------------------
>
>                 Key: CALCITE-2358
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2358
>             Project: Calcite
>          Issue Type: Bug
>          Components: druid
>            Reporter: slim bouguerra
>            Assignee: slim bouguerra
>            Priority: Major
>
> With the new ability to support null values in Druid, empty string is not equal to null anymore.
> To enable auto format parser {code}timestamp_parse{code} Druid function expects null literal as format argument.
> I have added a connection config parameter to allow smooth transition from old Druid version to version 0.13.0 and above.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)