[jira] [Updated] (CALCITE-2358) Use null literal instead of empty string as argument for timestamp_parse Druid expression
[
https://issues.apache.org/jira/browse/CALCITE-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Volodymyr Vysotskyi updated CALCITE-2358:
-
Fix Version/s: 1.17.0
> 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
> Fix For: 1.17.0
>
>
> 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)
[jira] [Updated] (CALCITE-2358) Use null literal instead of empty string as argument for timestamp_parse Druid expression
[
https://issues.apache.org/jira/browse/CALCITE-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
slim bouguerra updated CALCITE-2358:
Description:
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.
was:
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.
> 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)
[jira] [Updated] (CALCITE-2358) Use null literal instead of empty string as argument for timestamp_parse Druid expression
[
https://issues.apache.org/jira/browse/CALCITE-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
slim bouguerra updated CALCITE-2358:
Description:
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.
was:
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_parser{code} Druid function
expects null literal as format argument.
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
