You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Zoltan Haindrich (Jira)" <ji...@apache.org> on 2020/10/02 13:03:00 UTC

[jira] [Resolved] (HIVE-24157) Strict mode to fail on CAST timestamp <-> numeric

     [ https://issues.apache.org/jira/browse/HIVE-24157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zoltan Haindrich resolved HIVE-24157.
-------------------------------------
    Fix Version/s: 4.0.0
       Resolution: Fixed

merged into master. Thank you Jesus for reviewing the changes!

> Strict mode to fail on CAST timestamp <-> numeric
> -------------------------------------------------
>
>                 Key: HIVE-24157
>                 URL: https://issues.apache.org/jira/browse/HIVE-24157
>             Project: Hive
>          Issue Type: Improvement
>          Components: SQL
>            Reporter: Jesus Camacho Rodriguez
>            Assignee: Zoltan Haindrich
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> There is some interest in enforcing that CAST numeric <\-> timestamp is disallowed to avoid confusion among users, e.g., SQL standard does not allow numeric <\-> timestamp casting, timestamp type is timezone agnostic, etc.
> We should introduce a strict config for timestamp (similar to others before): If the config is true, we shall fail while compiling the query with a meaningful message.
> To provide similar behavior, Hive has multiple functions that provide clearer semantics for numeric to timestamp conversion (and vice versa):
> https://cwiki.apache.org/confluence/display/Hive/LanguageManual+UDF#LanguageManualUDF-DateFunctions



--
This message was sent by Atlassian Jira
(v8.3.4#803005)