[
https://issues.apache.org/jira/browse/HIVE-28632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Araika Singh updated HIVE-28632:
--------------------------------
Description:
_Boolean:_ Before HIVE-21240, the json deserializer implicitly converted
boolean strings without checking case sensitivity, resulting in {{false}} for
other strings. Now, this behavior changed to be case-sensitive, resulting in
{{false}} for all other strings. This behavior needs to be maintained in the
current version.
_Binary:_ Before HIVE-21240, any binary value in JSON was decoded to the
required value. Currently, we are not parsing the same. This needs to be fixed
to restore the previous behavior.
was:
_Boolean:_ Before HIVE-21240, the code implicitly converted boolean strings
without checking case sensitivity, resulting in {{false}} for other strings.
Now, this behavior changed to be case-sensitive, resulting in {{false}} for all
other strings. This behavior needs to be maintained in the current version.
_Binary:_ Before HIVE-21240, any binary value in JSON was decoded to the
required value. Currently, we are not parsing the same. This needs to be fixed
to restore the previous behavior.
> Fix issues in JSON SerDe implementations related to Boolean, Binary data types
> ------------------------------------------------------------------------------
>
> Key: HIVE-28632
> URL: https://issues.apache.org/jira/browse/HIVE-28632
> Project: Hive
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Reporter: Araika Singh
> Assignee: Araika Singh
> Priority: Major
>
> _Boolean:_ Before HIVE-21240, the json deserializer implicitly converted
> boolean strings without checking case sensitivity, resulting in {{false}} for
> other strings. Now, this behavior changed to be case-sensitive, resulting in
> {{false}} for all other strings. This behavior needs to be maintained in the
> current version.
> _Binary:_ Before HIVE-21240, any binary value in JSON was decoded to the
> required value. Currently, we are not parsing the same. This needs to be
> fixed to restore the previous behavior.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
