Hi @SparkRocks At the moment there is no such processor but there are ongoing discussions on the subject [1]. The best output format really depends of what you want to do with the data, JSON looks like a good format to me for its flexibility. If you really want CSV, there are multiple options depending of how complicated is your input data. If there are not a lot of tables/columns, you could do something like: ExecuteSQL > AvroToJson > EvaluateJsonPath (to extract the values into flow file attributes) > ReplaceText to write your CSV using expression language > PutS3 Otherwise you could have a look to ExecuteScript processor and rely on an existing library to perform the conversion. Or, as you suggested, you could write a custom processor and you could contribute your code to NiFi. [1] https://issues.apache.org/jira/browse/NIFI-1372 Hope this helps. ... View more

Hi @Manikandan Durairaj To update the name of the file, you can use an UpdateAttribute processor and set the attribute 'filename' with the name of your choice using expression language [1]. If you want a name based on current time, you can use date functions, otherwise you can use the function UUID to generate a unique filename for each flow file. That would be a property filename with ${UUID()} [1] https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html Hope this helps. ... View more

Hi @Manikandan Durairaj, I'd suggest you to read the following posts: https://developers.facebook.com/docs/graph-api/using-graph-api https://developers.facebook.com/docs/graph-api/common-scenarios https://developers.facebook.com/docs/facebook-login/access-tokens I'd try something like: https://graph.facebook.com/search?q=%23YOU-HASH-VALUE&limit=10000&access_token=YOUR-ACCESS-TOKEN Hope this helps. ... View more

Hi @milind pandit, Yes you just need to have core-site and hdfs-site configuration files available on your NiFi nodes for your PutHDFS processor. And obviously that network connections are OK between NiFi and HDP. Hope this helps. ... View more