[
https://issues.apache.org/jira/browse/YARN-4224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15086273#comment-15086273
]
Varun Saxena commented on YARN-4224:
------------------------------------
[~sjlee0], just carrying on from today's discussion.
I think "$", "!" and "*" might be fair choices for delimiters as well. If I am
not wrong, they are safe as well.
I agree we can give up on making it configurable.
What if the UID have the delimiter will choose. I guess asking the
application(client side) to escape it with the another safe character of our
choice should be good enough.
i.e. if say we choose delimiter to be ! and flow UID which is of the form
{{<cluster>\!<user>\!<flow>}} has user component as {{a!b*!c}}, then client can
encode it by *(say).
So, UID with a!b*!c as user would be sent as {{cluster!a*!b**!c!flow}}. We
should be able to parse it.
But should we make the UID key itself configurable ? This is regarding the key
we choose to store UID against in info field(in response).
Regarding entity type, [~gtCarrera9], are you fine with having it as part of
URL(as a mandatory param) ? I would prefer to have it as part of URL if there
is no use case. [~sjlee0], what you think on this ?
> Support fetching entities by UID and change the REST interface to conform to
> current REST APIs' in YARN
> -------------------------------------------------------------------------------------------------------
>
> Key: YARN-4224
> URL: https://issues.apache.org/jira/browse/YARN-4224
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Varun Saxena
> Assignee: Varun Saxena
> Labels: yarn-2928-1st-milestone
> Attachments: YARN-4224-YARN-2928.01.patch,
> YARN-4224-feature-YARN-2928.wip.02.patch,
> YARN-4224-feature-YARN-2928.wip.03.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
