Hi @LorencH ,   I'm of the opinion that if security is a concern (as it should be for any deployment) you should never rely on the permissions that come within the tarball. Your deployment procedure, automated or not, should always extract the files and explicitly "chown" and "chmod" the appropriate files to set the desired ownership and permissions.   I don't know of the reasons to eliminate the tarball, though.   Cheers, André   ... View more

@shashikumar Although I do not recommend this, due to creating confusion, you certainly can symlink the file paths on any linux system.   Just be sure the permissions are correct on the final new path, then create the symlink back to the old paths. ... View more

Thank you @steven-matison  This is really helpful.. /\  And If you allow me, I have a different question regarding Nifi CaptureChangeMySQL.. the username in this processor, should be the one with highest privileges/ root user ? because it is not mentioned anywhere in the help section (https://nifi.apache.org/docs/nifi-docs/components/org.apache.nifi/nifi-cdc-mysql-nar/1.5.0/org.apache.nifi.cdc.mysql.processors.CaptureChangeMySQL/ )   And when i provide a user credentials who has GRANT ALL PRIVILEGES ON *.*  then it is able to access CDC bin logs But getting permission denied when trying to access with a user who has only read permissions on *.*   Since the processor has nothing to do with write, i thought only read permissions were enough, but looks like its not the case.. Can you please throw some light in this regard.. ... View more

@Nifi_Al Its hard to guess here without seeing your flow, but i think here are a few ideas to resolve:   Use GenerateFlowFIle with content of the json you want to send to PutElasticsearchHttp Use AttributesToJson to write attribute to content of flowfile, then send that to PutElasticsearchHttp   To test basic connectivity, i would use the first method, then build a working flow from there.  I always work in small operational samples when trying to figure out how to configure a certain processor. ... View more

I think you will also need to do the transfer/commit in the each list logic ... View more

@AbhishekSingh I believe you can accomplish this with some very complicated Expression Language chaining.  It is possible to have many Expression Languages combined into one expression.   Reference:   https://nifi.apache.org/docs/nifi-docs/html/expression-language-guide.html   I do not have time to prove this out, but in theory,  you would combine lesson learned in your other post (expression language to change the database.table with Replace, ifElse and maybe Equals to get your desired outcome. ... View more

@Tryfan  You mention this file comes in daily.  You also mention that this file arrives through a load-balancer so you don't know which node will receive it.  This means you can't configure your source processor for "primary node" only execution as you have done in your shared sample flow with the ListFile.   As Primary Node only, the elected primary node will be the only node that executes that processor.  So if the source file lands on any other node, it would not get listed. You could handle this flow in the following manor: GetFile ---> (7 success relationships) PostHTTP or InvokeHTTP (7 of these with one configured for each node in your cluster cluster) ListenHTTP --> UpdateAttribute --> PutFile So in this flow, no matter which node receives your source file, the GetFile will consume it. It will then get cloned 6 times (7 copies then exist) with one copy of the FlowFile getting routed to 7 unique PostHttp processors.  Each of these targets the ListenHTTP processor listening on each node in your cluster. That ListenHTTP processor will receive all 7 copies (one copy per node) of the original source file.  Then use the UpdateAttribute to set your username and location info before the putFile which place each copy in the desired location on the source node.   If you add or remove nodes from your cluster, you would need to modify this flow accordingly which is a major downside to such a design.  Thus the best solution is still one where the source file is placed somewhere all nodes can retrieve it from so it scales automatically. If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt   ... View more