You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2013/10/07 04:24:49 UTC

[jira] [Updated] (HIVE-4777) Null value Versus RuntimeException in failed data type converting

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

Thejas M Nair updated HIVE-4777:
--------------------------------

    Fix Version/s:     (was: 0.12.0)

Preparing for 0.12 release. Removing fix version of 0.12 for those that are not in 0.12 branch.


> Null value Versus RuntimeException in failed data type converting
> -----------------------------------------------------------------
>
>                 Key: HIVE-4777
>                 URL: https://issues.apache.org/jira/browse/HIVE-4777
>             Project: Hive
>          Issue Type: Improvement
>          Components: Serializers/Deserializers
>            Reporter: Cheng Hao
>            Priority: Minor
>
> Usually "null" value will returns if the data can not be converted to the other type. (e.g. null == doubleConverter.convert("abc")).
> But it also may also throws RuntimeException other than NumberFormatException in the DoubleConverter.convert() method, as the type BINARY can not be converted into DOUBLE. And there are some others. (Check PrimitiveObjectInspectorUtils.java for details.)
> It's acceptable for throwing exception, but may not in runtime, as the data type convertibility can be decided before the data arrives. The earlier stage the better. 
> Or just like the normal case, return null constantly for the in-convertible data types converting.
> What do you think?
> Thanks,
> Hao



--
This message was sent by Atlassian JIRA
(v6.1#6144)