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

[jira] [Commented] (HIVE-24778) Unify hive.strict.timestamp.conversion and hive.strict.checks.type.safety properties

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

Stamatis Zampetakis commented on HIVE-24778:
--------------------------------------------

The quickest solution would be to remove {{hive.strict.timestamp.conversion}} in favor of {{hive.strict.checks.type.safety}} and refactor code accordingly. Another idea would be to split {{hive.strict.checks.type.safety}} into multiple props but this would bloat the configuration so I don't think that's a good idea. Last we could  change the property (or introduce a new one) and instead of boolean value accept a class (of a new interface) or something along these lines giving finer control to the user.

> Unify hive.strict.timestamp.conversion and hive.strict.checks.type.safety properties
> ------------------------------------------------------------------------------------
>
>                 Key: HIVE-24778
>                 URL: https://issues.apache.org/jira/browse/HIVE-24778
>             Project: Hive
>          Issue Type: Improvement
>    Affects Versions: 4.0.0
>            Reporter: Stamatis Zampetakis
>            Priority: Major
>             Fix For: 4.0.0
>
>
> The majority of strict type checks can be controlled by {{hive.strict.checks.type.safety}} property. HIVE-24157 introduced another property, namely  {{hive.strict.timestamp.conversion}}, to control the implicit comparisons between numerics and timestamps.
> The name and description of {{hive.strict.checks.type.safety}} imply that the property covers all strict checks so having others for specific cases appears confusing and can easily lead to unexpected behavior.
> The goal of this issue is to unify those properties to facilitate configuration and improve code reuse.



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