@ushasri You should check out NiFI Registry:   https://nifi.apache.org/registry.html   Using NiFi Registry you are able to version control flows during development.  Using same Nifi Registry you can now deploy these flows to other environment(s) such as your Cloudera licensed version (HDF,CDF,CFM).      Additionally, XML templates are going away.  In modern versions of nifi, you should use the Create Flow Definition, and transfer these JSON definition files manually between environments and/or nifi developers.       Other CI/CD DFLC (Data Flow Lifecycle) concepts for deploying flows across environments are using NIFI CLI API programmatically to do manual deployment operations.  We also often seen some level of integration between Github and NiFi Registry. ... View more

Can't wait for this event!  Let's go!! ... View more

@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

@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

@Fahmihamzah84 This appears to be an issue with your schema.  The BigQuery error is suggesting an issue trying to cast a string into a collection (array/list/ect).   It's hard to tell which array may be causing the issue as there are many.   My suggestion is to set the processor to log level DEBUG and see if you can get more verbose error.   This will help you figure out which field or fields is the culprit.      Keep in mind it could be one of the empty arrays too.     I do not suggest the following as a solution just as path to figuring out where the problem is.  Sometimes when i have issues with type casting,  i make everything a string temporarily and for development.  If you do this carefully one at a time, when the error goes away, you can determine which field it is.   This also helps you identify a working state for your flow and allow you to work from that operational base to find solution for the end schema being the format you need. ... View more

Awesome news, +2 solutions here.   ... View more