hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From varunsax...@apache.org
Subject [49/50] [abbrv] hadoop git commit: YARN-5577. [Atsv2] Document object passing in infofilters with an example (Rohith Sharma K S via Varun Saxena)
Date Wed, 30 Aug 2017 20:16:14 GMT
YARN-5577. [Atsv2] Document object passing in infofilters with an example (Rohith Sharma K
S via Varun Saxena)

(cherry picked from commit ea29e3bc27f15516f4346d1312eef703bcd3d032)


Project: http://git-wip-us.apache.org/repos/asf/hadoop/repo
Commit: http://git-wip-us.apache.org/repos/asf/hadoop/commit/48d65e51
Tree: http://git-wip-us.apache.org/repos/asf/hadoop/tree/48d65e51
Diff: http://git-wip-us.apache.org/repos/asf/hadoop/diff/48d65e51

Branch: refs/heads/YARN-5355_branch2
Commit: 48d65e51b3b437d968ab1d9097b01bc66290919c
Parents: 1a748b6
Author: Varun Saxena <varunsaxena@apache.org>
Authored: Mon Sep 19 14:33:06 2016 +0530
Committer: Varun Saxena <varunsaxena@apache.org>
Committed: Thu Aug 31 01:41:59 2017 +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/48d65e51/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 b3df844..66bb7f9 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
@@ -781,6 +781,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 {"&lt;key&gt;":"&lt;value&gt;","&lt;key&gt;":"&lt;value&gt;"...}).<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.
@@ -906,6 +908,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 {"&lt;key&gt;":"&lt;value&gt;","&lt;key&gt;":"&lt;value&gt;"...}).<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.
@@ -1104,6 +1108,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 {"&lt;key&gt;":"&lt;value&gt;","&lt;key&gt;":"&lt;value&gt;"...}).<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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-commits-help@hadoop.apache.org


Mime
View raw message