Good Day This is Cazen It's related on "HIVE-11825 <https://issues.apache.org/jira/browse/HIVE-11825> get_json_object(col,'$.a') is null in where clause didn`t work"
When UDF read JSON format, it calls org.codehaus.jackson.map.ObjectMapper And, exception occured when meet wrong escape character(org.codehaus.jackson.JsonParseException: Unrecognized character escape) For example in HIVE-11825, There are "keywords":"思科Q4收入估\$79.2亿 前景阴云笼罩" in JSON, so when parser meet \$, it cause JsonParseException. It can evade just set on ALLOW_BACKSLASH_ESCAPING_ANY_CHARACTER property - JSON_FACTORY.enable(Feature.ALLOW_BACKSLASH_ESCAPING_ANY_CHARACTER) I think it's some harsh. Of course I know it's unstandard JSON format. There are some logic needed when store JSON. Is there any reason that have a rule of strict JSON format? I'm newbie in Hive history, so want to ask via mailling list Thank you very much -- ca...@korea.com cazen....@samsung.com http://www.Cazen.co.kr <http://www.cazen.co.kr/>
