You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Xuefu Zhang (JIRA)" <ji...@apache.org> on 2013/10/04 05:17:44 UTC
[jira] [Updated] (HIVE-5438) Introduce different server modes for
error handling in Hive server2
[ https://issues.apache.org/jira/browse/HIVE-5438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xuefu Zhang updated HIVE-5438:
------------------------------
Description:
Currently Hive handles errors such as divide-by-zero, numeric overflow/iunderflow, type conversion, etc. by putting null values. While the behaviours isn't consistent all the time (see HIVE-5436 as an example), which needs to be addressed, it's desirable to introduce different server modes and allow user to choose different error handling. For instance, instead of null, MAX value may be placed in case of number overflow. Also, warnings or errors can be given in error handling.
Major databases have such settings. For example, mysql has a setting for data overflow and a setting specifically for divide-by-zero. It's desirable for Hive to give such flexibility to the user.
The existing mode can be thought as a default or strict mode.
was:
Currently Hive handles errors such as divide-by-zero, numeric overflow/iunderflow, type conversion, etc. by putting null values. While the behaviours isn't consistent all the time (see HIVE-5436 as an example), which needs to be addressed, it's desirable to introduce different server modes and allow user to choose different error handling. For instance, instead of null, MAX value may be placed in case of number overflow.
Major databases have such settings. For example, mysql has a setting for data overflow and a setting specifically for divide-by-zero. It's desirable for Hive to give such flexibility to the user.
> Introduce different server modes for error handling in Hive server2
> -------------------------------------------------------------------
>
> Key: HIVE-5438
> URL: https://issues.apache.org/jira/browse/HIVE-5438
> Project: Hive
> Issue Type: New Feature
> Components: HiveServer2
> Affects Versions: 0.11.0
> Reporter: Xuefu Zhang
> Assignee: Xuefu Zhang
>
> Currently Hive handles errors such as divide-by-zero, numeric overflow/iunderflow, type conversion, etc. by putting null values. While the behaviours isn't consistent all the time (see HIVE-5436 as an example), which needs to be addressed, it's desirable to introduce different server modes and allow user to choose different error handling. For instance, instead of null, MAX value may be placed in case of number overflow. Also, warnings or errors can be given in error handling.
> Major databases have such settings. For example, mysql has a setting for data overflow and a setting specifically for divide-by-zero. It's desirable for Hive to give such flexibility to the user.
> The existing mode can be thought as a default or strict mode.
--
This message was sent by Atlassian JIRA
(v6.1#6144)