@MaarufB Using nifi-cli outside of curl on a nifi node is definitely a challenge.  There are a lot of things you need to check.  Most of them are addressed in a similar post here:   https://community.cloudera.com/t5/Support-Questions/Calling-nifi-Api-using-Postman/td-p/343993   Hopefully you can find the solution within that post.   ... View more

@yoiun Going to go out on a ledge here:  It seems like the the sqoop command and hue/sqoop command are executed on different hosts.  Does the new host have permissions to mysql?   This error here: Access denied for user 'demo'@'152.30.119.754' leads me to believe it does not. ... View more

@i_am_dba  This is a very difficult one to explain.  I think the issue is the string schema, or removing the avro schema you mentioned.  My first suggestion would be to try to specific the schema which should help getting the data into the right formats.   An alternate solution is to try and do that manually by replacetext/regex,etc but that is not the ideal solution.   That said, another higher level suggesting is to update the upstream datasource to permanently solve the instability from '' (blank string), 'null' (string), or actual NULL (not a blank, '', or string at all). ... View more

@MaarufB Please make a new post with as much detail as you can around your question and use case.  This is an old topic and will not get a good response in the comments.  Feel free to @ tag me in the new post. ... View more

@sathish3389 Its not entirely clear what you are asking here but I will give it a go.   ListenHttp is used to listen to an http port with POST limited capabilities.   If you are looking post data to nifi as more of REST API, you may want to check out HandleHttpRequest and HandleHttpResponse, as they have a bit more capability, and some ssl client authentication requirements.  They also allow you to program authentication logic before returning the response.   To do that. you would build your data flow (after HandleHttpRequest) to look for an authentication (user,password,key,etc) header, validate that and then if valid, continue to HandleHttpResponse with 200 (success).  An invalidate authentication header would then go to HandleHttpResponse with 500 (error).  An invalid request (wrong path, missing info, etc) could be routed to HandleHttpReponse with 404 (invalid).   ... View more

@raniaa Ambari is no longer part of the Cloudera ecosystem of tools/products.  I would recommend you look for community support for ambari on stackoverflow or the ASF Slack. ... View more

@leandrolinof    FetchFile is going to look for the file on the nifi node or nifi nodes where nifi is installed.  This is usually something done on the primary node of a multi node nifi cluster.   If you want to connect to another linux server, not part of the nifi cluster you will have to take a different approach.  One such approach could be using minifi, or possible ExecuteScript to run a linux command from nifi node to other linux server. ... View more

@morti I believe the answer is yes.  For example,  if i query a database, and get results as content, that schema for those results is an attribute of the flowfile holding the content.  Additionally,  i could add attributes in my flow based on certain conditions, or other attributes, or even the content from prev processors. ... View more