You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Denys Kuzmenko (Jira)" <ji...@apache.org> on 2026/10/15 18:54:00 UTC
[jira] [Updated] (HIVE-30179) JsonSerDe and json_read: read and write VARIANT as JSON
[ https://issues.apache.org/jira/browse/HIVE-30179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denys Kuzmenko updated HIVE-30179:
----------------------------------
Description:
Today JsonSerDe writes a VARIANT column as its two-binary encoding: {"metadata":"<base64>","value":"<base64>"}.
json_read(json, 'variant') reads only that form.
- Proposal: write the variant's JSON value, and read any JSON value into a variant (the parse_json path).
- Compatibility: files written in the two-binary form must still be readable, e.g. by recognising an object with
exactly the base64 metadata/value fields, or behind a table property.
> JsonSerDe and json_read: read and write VARIANT as JSON
> -------------------------------------------------------
>
> Key: HIVE-30179
> URL: https://issues.apache.org/jira/browse/HIVE-30179
> Project: Hive
> Issue Type: Sub-task
> Reporter: Denys Kuzmenko
> Priority: Major
>
> Today JsonSerDe writes a VARIANT column as its two-binary encoding: {"metadata":"<base64>","value":"<base64>"}.
> json_read(json, 'variant') reads only that form.
> - Proposal: write the variant's JSON value, and read any JSON value into a variant (the parse_json path).
> - Compatibility: files written in the two-binary form must still be readable, e.g. by recognising an object with
> exactly the base64 metadata/value fields, or behind a table property.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)