hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <>
Subject [jira] [Commented] (HIVE-11483) Add encoding and decoding for query string config
Date Thu, 13 Aug 2015 05:00:48 GMT


Amareshwari Sriramadasu commented on HIVE-11483:

bq. but does any current Hive behavior depend on this? Or are you worried about external tools
depending on it?
The only current behavior is for logging, which we can fix by calling HiveConf.getDecodedString().
If there are no external tools consuming (i hope they are not), I think adding one config
to say whether to encode or not - is unnecessary. But not to break any, I'm fine adding one
more config.

+1 for URL encoding then, as it is reasonably human readable.

> Add encoding and decoding for query string config
> -------------------------------------------------
>                 Key: HIVE-11483
>                 URL:
>             Project: Hive
>          Issue Type: Improvement
>          Components: Query Processor
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Akshay Goyal
> We have seen some queries in production where some of the literals passed in the query
have control characters, which result in exception when query string is set in the job xml.
> Proposing a solution to encode the query string in configuration and provide getters
decoded string.
> Here is a commit in a forked repo :
> Suggestions are welcome on the solution.

This message was sent by Atlassian JIRA

View raw message