[
https://issues.apache.org/jira/browse/YARN-6593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110248#comment-16110248
]
Jian He commented on YARN-6593:
-------------------------------
The use-case is to be able to select containers based on key and values, say, I
want to find my containers with version=v1, and env= test, and name=web1 or
name = web2. Yes, currently it's a set of values not a single value, I
misspoke.
We can still make it work by searching the entire string as Arun said. But
that's not explicit. The AM, client, or even UI then needs to parse the string
to extract the keys and values.
I was thinking this change will affect this jira's implementation also, hence
continue commenting here. If you think this anyways can be revisited. We can
commit this first and work on it in YARN-6594. It doesn't matter to me.
> [API] Introduce Placement Constraint object
> -------------------------------------------
>
> Key: YARN-6593
> URL: https://issues.apache.org/jira/browse/YARN-6593
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Konstantinos Karanasos
> Assignee: Konstantinos Karanasos
> Attachments: YARN-6593.001.patch, YARN-6593.002.patch,
> YARN-6593.003.patch, YARN-6593.004.patch, YARN-6593.005.patch,
> YARN-6593.006.patch, YARN-6593.007.patch, YARN-6593.008.patch
>
>
> Just removed Fixed version and moved it to target version as we set fix
> version only after patch is committed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
