[HIVE-5438] Introduce different server modes for error handling in Hive server2

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 0.11.0
• Component/s: HiveServer2
• Assignee: Xuefu Zhang
• Reporter: Xuefu Zhang
• Created: 04/Oct/13 03:14
• Updated: 07/Oct/22 23:48

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.

Issue Links

• is related to: HIVE-5656 Hive produces unclear, confusing SemanticException when dealing with mod or pmod by zero
• relates to: HIVE-5660 Hive incorrecly handles data overflow/underflow
• relates to: CALCITE-525 Exception-handling in built-in functions
• relates to: HIVE-5655 Hive incorrecly handles divide-by-zero case