Short Answer #

Absolutely! Starting with Hive 2.3.0, ACID transactional ORC tables support partial updates to nested complex types like Maps and Arrays—you don’t need to overwrite the entire Map, Array, or row to modify specific elements.

Prerequisites #

First, confirm your setup checks these boxes:

• Hive version 2.3.0 or newer
• Your table is a transactional ORC table (you already have this configured with TBLPROPERTIES ("transactional"="true") and STORED AS ORC)
• Remember: Hive Arrays are 1-indexed (don’t use 0-based indices like you would in most programming languages—this is a common gotcha!)

Step-by-Step Example: Update a Specific Array Element in a Map #

Using your existing table complex_nested_types_update_array_map, let’s update the 2nd element of the array mapped to Tomas for person_id=2:

Update Statement

UPDATE complex_nested_types_update_array_map
SET person_info['Tomas'][2] = '+1111111111'
WHERE person_id = 2;

Verify the Result

Run your select query again:

SELECT * FROM complex_nested_types_update_array_map ORDER BY person_id;

You’ll see only the targeted array element is changed:

1 {"John":["+44801123311","+120342234","+230342234","+3303422434"]}
2 {"Tomas":["+380342234","+1111111111","+230342234","+530342234"]}

Update Multiple Elements at Once #

You can modify multiple nested elements in a single UPDATE statement too. For example, update the 3rd and 4th elements of Tomas’s array:

UPDATE complex_nested_types_update_array_map
SET person_info['Tomas'][3] = '+2222222222',
    person_info['Tomas'][4] = '+3333333333'
WHERE person_id = 2;

What If the Map Key Doesn’t Exist? #

If you try to update a Map key that isn’t present (e.g., person_info['Amy'][1] for person_id=2), Hive will add the new key to the Map with the specified array element. For example:

UPDATE complex_nested_types_update_array_map
SET person_info['Amy'][1] = '+4444444444'
WHERE person_id = 2;

The result would include both Tomas and Amy in the Map:

2 {"Tomas":["+380342234","+1111111111","+2222222222","+3333333333"], "Amy":["+4444444444"]}

Key Notes to Avoid Pitfalls #

• Indexing: Always use 1-based indices for Hive Arrays—using 0 will throw an error.
• ACID/ORC Requirement: Partial updates only work with transactional ORC tables; other storage formats (like Parquet) don’t support this feature as of current Hive versions.
• Performance: Partial updates are far more efficient than overwriting the entire Map/row, especially for large nested structures, since Hive only modifies the targeted elements instead of rewriting the entire record.

内容的提问来源于stack exchange，提问作者Konstantin Harasov