[
https://issues.apache.org/jira/browse/OOZIE-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13537888#comment-13537888
]
Alejandro Abdelnur commented on OOZIE-1141:
-------------------------------------------
A DB update can be required if doing a major upgrade, Oozie3 to Oozie4. So, if
we are shooting HCAT for Oozie4 we are good. Hcat integration is already making
schema changes, right? If so we should be good with a DB update.
Still, the symbols that don't require URL/XML encoding are: -._~:#[]@!$'()+,;=
We could use +, $, ! or @.
> Escaping Ampersand in the HCat URI to bypass XML validation
> -----------------------------------------------------------
>
> Key: OOZIE-1141
> URL: https://issues.apache.org/jira/browse/OOZIE-1141
> Project: Oozie
> Issue Type: Sub-task
> Reporter: Mona Chitnis
> Assignee: Mona Chitnis
> Fix For: trunk
>
>
> Uncovered during end-to-end testing. In an HCat URI like this
> hcat://<server>:<port>/db/table/partition1=abc&partition2=xyz, the '&'
> between the partition key-value pairs, fails XML validation. It needs to be
> escaped - but keeping in mind
> 1. HCat URIs are stored as missing dependencies in database. Each time they
> are retrieved, the logic needs to check for the escaping (very frequent and
> increases overhead)
> 2. When displaying back to the user his missing dependencies, the original
> unescaped URI should be shown.
> Alternatives for approach:
> 1. Asking the user to use the encoded string "&" in his URI-template is a
> usability-killer.
> 2. The other alternative is to use some other separator instead of ampersand,
> which does not conflict existing separators in Oozie, such as colon (:), but
> it is highly non-intuitive in a URI
> Therefore to me, the lesser of two evils seems to do escape logic during XML
> validation, storing separator as something else internally for db retrievals,
> and again showing original '&' for display to user.
> Please provide your thoughts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
