@FediMannoubi Get the required response data that you need from flowfile to an attribute with EvaluateJsonPath.  Do this for user, password, and token.     Once these  data values are attributes,  you can use them in the header, or write them back out to the flowfile content when appropriate. ... View more

@harry_12 I believe that users which are created in Ambari are for logging into ambari UI. If you need an SSH user for a particular host, you should create that user in the node(s) operating system directly. ... View more

@JagadeeshJinka I believe the solution here is an entry in the /etc/hosts file on all nifi nodes.  Based on above that could possible be:   172.27.130.4 es-saas-es-http.saas.svc.cluster.local     However i would recommend fully qualified domains (FQDNS. for example saas.somedomain.com) with matching DNS entries, and SSL certs ... View more

@YasBHK HDP is no longer supported, there will be no releases and no upgrades.   I highly recommend not solutioning or training on the HDP Sandbox.   I would recommend that you investigate the modernized alternatives to HDP, such as CDP Private Cloud Base or CDP Public Cloud. ... View more

@udayabaski  This sounds like a job for DistributedMapCache.  Using this, you can set key/value pairs for start and end time at one point in the flow, and access them in other parts of the flow.   Here are some important docs to get you started :   https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-distributed-cache-services-nar/1.20.0/org.apache.nifi.distributed.cache.server.map.DistributedMapCacheServer/index.html https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.20.0/org.apache.nifi.processors.standard.PutDistributedMapCache/index.html https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-standard-nar/1.20.0/org.apache.nifi.processors.standard.FetchDistributedMapCache/index.html         ... View more

 @cotopaul   - Thanks for being such a community superstar!! @swanifi in addition to above, In the future please be sure to include screen shot of the processor property and configurations. One thing that i think you could achieve is some type of an upstream gate on the flow files, so that they are released in blocks that satisfy the expectation of 1000 records per operation.    I am not aware if this is configureable within the processor.    ... View more

@bennour This error is an issue with your database endpoint ssl.   My first suggestion is to use the following arugment in your sqoop command:   useSSL=false   then if this doesn't work, focus on getting a proper ssl certificate for the host.     ... View more

The file you need to send or upload to the api, should be the content of your flowfile that routes into InvokeHttp.   So some upstream process should read the file, and send the content through success relationship to InvokeHttp.   For example if this file is json,  I use GenerateFlowFile processor, put the json contents in there, then send to InvokeHttp. ... View more

@Techie123 to add headers in invokeHttp just click the + sign to add a new dynamic property, and set key to "Content-Type" and value to "multipart/form-data".   You will also need to make sure the rest of your invokeHttp is confirmed correctly.  Depending on your version, you can also create and send an attribute called "Content-Type" of the same value.  Newest versions of NiFi will see a default property "Request Content-Type" which can also be set to attribute $mime-type which you can also define to suit your API.     One other suggestion,  make sure you are testing remote API Calls with something like postman to confirm all the required values.   Then, work with NiFi after you have a known operational understanding for the api. ... View more