hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-11483) Add encoding and decoding for query string config
Date Wed, 12 Aug 2015 14:46:45 GMT

    [ https://issues.apache.org/jira/browse/HIVE-11483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14693611#comment-14693611
] 

Alan Gates commented on HIVE-11483:
-----------------------------------

bq. How do we distinguish between actual ^A with control-A ? And how to decode them back
I was assuming the query was for human consumption only.  I like URL encoding as there is
tool support for it and it's reasonably human readable.

bq. I think this should not break the existing behaviour
Agreed, but does any current Hive behavior depend on this?  Or are you worried about external
tools depending on it?

> Add encoding and decoding for query string config
> -------------------------------------------------
>
>                 Key: HIVE-11483
>                 URL: https://issues.apache.org/jira/browse/HIVE-11483
>             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 : https://github.com/InMobi/hive/commit/2faf5761191fa3103a0d779fde584d494ed75bf5
> Suggestions are welcome on the solution.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message