[
https://issues.apache.org/jira/browse/HIVE-20375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764254#comment-16764254
]
BELUGA BEHR commented on HIVE-20375:
------------------------------------
I just ran into the same issue. The description is correct.
I am working on an overhaul of the entire JSON parser. Will take a look at
addressing this.
> Json SerDe ignoring the timestamp.formats property
> --------------------------------------------------
>
> Key: HIVE-20375
> URL: https://issues.apache.org/jira/browse/HIVE-20375
> Project: Hive
> Issue Type: Bug
> Affects Versions: 4.0.0
> Reporter: slim bouguerra
> Assignee: Ashutosh Chauhan
> Priority: Major
>
> JsonSerd is supposed to accept "timestamp.formats" SerDe property to allow
> different timestamp formats, after recent refactor I see that this is not
> working anymore.
> Looking at the code I can see that The serde is not using the constructed
> parser with added format
> https://github.com/apache/hive/blob/1105ef3974d8a324637d3d35881a739af3aeb382/serde/src/java/org/apache/hadoop/hive/serde2/json/HiveJsonStructReader.java#L82
> But instead it is using Converter
> https://github.com/apache/hive/blob/1105ef3974d8a324637d3d35881a739af3aeb382/serde/src/java/org/apache/hadoop/hive/serde2/json/HiveJsonStructReader.java#L324
> Then converter is using
> org.apache.hadoop.hive.serde2.objectinspector.primitive.PrimitiveObjectInspectorConverter.TimestampConverter
> This converter does not have any knowledge about user formats or what so
> ever...
> It is using this static converter
> org.apache.hadoop.hive.serde2.objectinspector.primitive.PrimitiveObjectInspectorUtils#getTimestampFromString
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
