@myoung ...in nifi i have used invoked http processor that get data from web app.. i want to apply the condition on json data file ...i means when the resource="abc" the alarm get filter and goes to one processor and other alarm will go to another processor.....so my question is what are the processor is required..as of now i have used one http invoked that will provide all the alarm form my web app ..two putfile processor for storing alarm one for resource="abc" and one for other resource. and i have also used one Routonatrribute processor for condition..in RoutOnAttribute config i have decalred on dynamic property whic is ....the name of property is alarms.resource and the value is ${alarms.resource:equals('abc')}  the below is respon of Invoked http processor...want the alarm that contain resource='abc' that will go to one put file processor { "alamrs" : [ { "correlate" : [ " " , " " , " " ], "event" : " " , "group" : " " , "history" : [ { "event" : " " , "href" : " " , "id" : " " , "resource" : " abc " , "status" : " " , "text" : " " , "type" : " " , "updateTime" : " " , "user" : " " , "value" : "--" } ], "href" : " " , "id" : "" , "rawData" : null , "receiveTime" : " " , "service" : [ " " ], "resource" : "abc" , "status" : " " , "tags" : [ "" ], "text" : " : " , "timeout" : , }, { "correlate" : [ " " , " " , " " ], "event" : " " , "group" : " " , "history" : [ { "event" : " " , "href" : " " , "id" : " " , "resource" : " abc " , "status" : " " , "text" : " " , "type" : " " , "updateTime" : " " , "user" : " " , "value" : "--" } ], "href" : " " , "id" : "" , "rawData" : null , "receiveTime" : " " , "service" : [ " " ], "resource" : "abc" , "status" : " " , "tags" : [ "" ], "text" : " : " , "timeout" : , }, { "correlate" : [ " " , " " , " " ], "event" : " " , "group" : " " , "history" : [ { "event" : " " , "href" : " " , "id" : " " , "resource" : " abc " , "status" : " " , "text" : " " , "type" : " " , "updateTime" : " " , "user" : " " , "value" : "--" } ], "href" : " " , "id" : "" , "rawData" : null , "receiveTime" : " " , "service" : [ " " ], "resource" : "abc" , "status" : " " , "tags" : [ "" ], "text" : " : " , "timeout" : , } @  ... View more

Thanks... It worked... ... View more

You can use as shown in below article - https://community.hortonworks.com/questions/23244/ranger-add-policies-via-rest-api.html ... View more

There are, but it seems that they are for Ranger internal use. There aren't any public APIs. Here is the public API documentation for Ranger 0.5. You can also take a look at the following classes if you're interested: org.apache.ranger.rest.PublicAPIs org.apache.ranger.rest.PublicAPIsv2 The UI is hitting some user and group endpoints, but it doesn't seem as if there is documentation around them. I wouldn't rely on them. ... View more

@Abraham Johnson @vpoornalingam There is still another reason and cure for this scenario (HDP-2.6.2.0-205). It can also happen that Ambari is looking for the pid files in the wrong place In my case the pid files were actually located at: /var/run/hadoop/hdfs-<clustername>/hadoop-hdfs-<clustername>-namenode.pid while ambari-agent would look at : /var/run/hadoop/hdfs/hadoop-hdfs-hdfs-namenode.pid In this state, with both the dir and the pid file name wrong, Ambari does not detect a running HDFS service, and you would also not be able to (re)start it. The pid file location is deduted from this snippet in hadoop-env.sh: export HADOOP_PID_DIR={{hadoop_pid_dir_prefix}}/$USER I have yet to find out why Ambari decided to change the value of $USER all of a sudden. ... View more