@Mohamed_Shaaban I recommend starting a new community question with the details specific to your setup. This allows the community to address/assist with your specific setup versus comparing your issue to what was shared in this post. Thanks, Matt
... View more
id, name, balance, join_date, notes 1, John, 48.23, 04/03/2007 "Our very first customer!" 2, Jane, 1245.89, 08/22/2009, 3, Frank Franklin, "48481.29", 04/04/2016, the logic may fail in the above case, if column contains multiple rows.
... View more
@Kushisabishii could you please advise what list of host needs to be provided on the NIFI_WEB_PROXY_HOST I have added the docker host and port that I access the NiFi UI. For example my NiFi is accessible via https://docker-host.comp.com/nifi/ Hence I have added the NIFI_WEB_PROXY_HOST = docker-host.comp.com:443 into my docker compose file. Do I need to consider any other hosts to be added ?
... View more
@drewski7 New processors are created within the community all the time and the documentation for processors should include resource considerations for CPU usage and Memory usage. Just because a processor list memory as a resource consideration, that impact is often a byproduct of how that processor has been configured. you can refer to the imbedded documentation in your installed NiFi instance or you can right click on a processor added to the canvas and select "view usage" from the displayed context menu to go directly to that components embedded documentation page. But processors like ReplaceText, SplitText, SplitContent, SplitJson,... would be examples. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more
@stupidnickname
All nodes in a NiFi cluster execute their own copy of the flow.xml.gz. I order for nodes to be members of the same NiFi cluster, all nodes must be running the flow.xml.gz file with same exact flow contents. Each node in a NiFi cluster loads its FlowFiles (FlowFiles are what traverse between one processor component to another and consist of metadata and content) and is unaware of the FlowFiles being processed by other nodes in a NiFi cluster. In a NiFi cluster there is the concept of a primary node. Some processors can be configured to execute on the primary node only. If the primary elected node goes down , a new node will be elected as primary node and those primary node only configured processors will start executing on that newly elected primary node. Perhaps more details around your query could help provide a more specific response if this does not answer your question.
If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you,
Matt
... View more
@kcc, as this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post.
... View more
@Jacccs An example or detailed description of yoru use case may be helpful in providing the bets guidance for you. While the NiFi Expression Language (NEL) function anyMatchingAttribute expects a java regular expression that searches and returns values for multiple FlowFile attributes, that does not appear to be what you need??? Your attribute "attributeToSearch" implies only a single specific FlowFile attribute is desire to be checked if it contains some "${value}". If this is correct, you would be able to use the following NEL: ${literal("${${attributeToSearch}}"):contains('${value}')} For above NEL, let's assume a FlowFile with attribute "attributeToSearch" set to "username". A FlowFile attribute "username" set to "admin-matt". A FlowFile attribute "value" set to "admin". The result of above NEL statement would be true ${$attributeToSearch}} would first resolve to ${username} which would then resolve to "admin-matt". That "admin-matt" string would be then passed to the NEL contains function which will to check to see if that string contains the string "admin" within it. The result is a boolean "true" or "false". If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more
@hegdemahendra This is not something I have tried before, but... When you execute the nifi.sh script to start it bootstrap the NiFi process via the configuration in the bootstrap.conf NiFi configuration file. It is during the bootstrap process that NiFi starts the main child process that loads NiFi. Perhaps you can add additional java.args to handle your pre NiFi needs? Or maybe modify the the nifi.sh script itself so that is executes your requirements before calling the rest of the NiFi startup process. If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped. Thank you, Matt
... View more
