Repository: hadoop Updated Branches: refs/heads/trunk 3552c2b99 -> ea29e3bc2
YARN-5577. [Atsv2] Document object passing in infofilters with an example (Rohith Sharma K S via Varun Saxena) Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/ea29e3bc Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/ea29e3bc Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/ea29e3bc Branch: refs/heads/trunk Commit: ea29e3bc27f15516f4346d1312eef703bcd3d032 Parents: 3552c2b Author: Varun Saxena <varunsax...@apache.org> Authored: Mon Sep 19 14:33:06 2016 +0530 Committer: Varun Saxena <varunsax...@apache.org> Committed: Mon Sep 19 14:33:06 2016 +0530 ---------------------------------------------------------------------- .../hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md | 6 ++++++ 1 file changed, 6 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/hadoop/blob/ea29e3bc/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md ---------------------------------------------------------------------- diff --git a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md index b6a0da4..6b7bd08 100644 --- a/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md +++ b/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md @@ -712,6 +712,8 @@ none of the apps match the predicates, an empty list will be returned. "eq" means equals, "ne" means not equals and existence of key is not required for a match and "ene" means not equals but existence of key is required. We can combine any number of ANDs' and ORs' to create complex expressions. Brackets can be used to club expressions together.<br/> _For example_ : infofilters can be "(((infokey1 eq value1) AND (infokey2 ne value1)) OR (infokey1 ene value3))".<br/> + Note : If value is an object then value can be given in the form of JSON format without any space.<br/> + _For example_ : infofilters can be (infokey1 eq {"<key>":"<value>","<key>":"<value>"...}).<br/> Please note that URL unsafe characters such as spaces will have to be suitably encoded. 1. `conffilters` - If specified, matched applications must have exact matches to the given config name and must be either equal or not equal to the given config value. Both the config name and value must be strings. conffilters are represented in the same form as infofilters. @@ -837,6 +839,8 @@ match the predicates, an empty list will be returned. "eq" means equals, "ne" means not equals and existence of key is not required for a match and "ene" means not equals but existence of key is required. We can combine any number of ANDs' and ORs' to create complex expressions. Brackets can be used to club expressions together.<br/> _For example_ : infofilters can be "(((infokey1 eq value1) AND (infokey2 ne value1)) OR (infokey1 ene value3))".<br/> + Note : If value is an object then value can be given in the form of JSON format without any space.<br/> + _For example_ : infofilters can be (infokey1 eq {"<key>":"<value>","<key>":"<value>"...}).<br/> Please note that URL unsafe characters such as spaces will have to be suitably encoded. 1. `conffilters` - If specified, matched applications must have exact matches to the given config name and must be either equal or not equal to the given config value. Both the config name and value must be strings. conffilters are represented in the same form as infofilters. @@ -1035,6 +1039,8 @@ If none of the entities match the predicates, an empty list will be returned. "eq" means equals, "ne" means not equals and existence of key is not required for a match and "ene" means not equals but existence of key is required. We can combine any number of ANDs' and ORs' to create complex expressions. Brackets can be used to club expressions together.<br/> _For example_ : infofilters can be "(((infokey1 eq value1) AND (infokey2 ne value1)) OR (infokey1 ene value3))".<br/> + Note : If value is an object then value can be given in the form of JSON format without any space.<br/> + _For example_ : infofilters can be (infokey1 eq {"<key>":"<value>","<key>":"<value>"...}).<br/> Please note that URL unsafe characters such as spaces will have to be suitably encoded. 1. `conffilters` - If specified, matched entities must have exact matches to the given config name and must be either equal or not equal to the given config value. Both the config name and value must be strings. conffilters are represented in the same form as infofilters. --------------------------------------------------------------------- To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-commits-h...@hadoop.apache.org
