About ckumar

ckumar · ‎05-19-2022

I believe MergeContent Merging Strategy is set to Defragment ? If it is set to Defragment then MergeContent will wait to receive all flow file part of fragment.count. so what happened to the remaining 2 flow files? which relationships they move? failure? and terminated on Processor itself assuming as per screenshot . If you wish to merge with reamaning 8 then Merging Strategy needs to be changed but that could be lead to case where all 8 records can not be merged together all the time since there is no correlation, or if you just want to merge all records irrespective of failure or success , then you need to have failure or success both relationships configured for MergeContent . Was your question answered? Please take some time to click on "Accept as Solution" below this post. If you find a reply useful, say thanks by clicking on the thumbs up button.

ckumar · ‎05-16-2022

With LB in place, you are reaching NiFi as anonymous when LB has not been configured to pass the user identity to NiFi that what I understand from looking the log snippet.. Please refer this page to check if proxy details are configured correctly https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#proxy_configuration

ckumar · ‎04-25-2022

Have you tested ListenFTP without setting SSLContextService? just to make sure supplied username and password is correct?

ckumar · ‎04-13-2022

There are two aspects of your question "How do you configure a PutMongo NiFi Processor " 1. Connection details: Connection URL, User Auth, Wire encryption (SSL ) 2. Actual Query: make sure query syntax is correct. If you can post an error snipped and snap from the processor config to be able to isolate if this query issue or connection issue. Assume if this is with query-related issue , then you can verify if the same query works from the generic mongo db client? if not then same query will not work from nifi:PutMongo as well. Thank You.

ckumar · ‎04-13-2022

You can receive values from http end point by using LisntHTTP in nifi which receives values through HTTP headers and stored in flow file attribute.

ckumar · ‎04-12-2022

NiFi as a service alone can not autoscale irrespective of the type public/private cloud provided until it is customized and managed by different automation and scaling applications over the public cloud. But Cloudera offers NiFi as Data flow Expreinace in the public cloud which does support autoscaling Please check https://docs.cloudera.com/dataflow/cloud/release-notes/topics/cdf-whats-new.html for more info. Thank You.

ckumar · ‎04-12-2022

also, you mentioned "Processor doesn't read saved attribute" Which specific processor you are complaining about ?

ckumar · ‎04-12-2022

trying to understand your flow pipeline with respect to your use case explanations, You have two upstream queued for InvokeHTTP , in one using ExtractText you are extracting text , which will be stored in flow file as an attribute then running HTTP Method from InvokeHTTP and configured Attributes to Send for the attributed which is created by ExtractText ? What GenreateFlowFile os doing in this flow? what evaluation is configured with EvaluateJsonPath ? Please provide more details

ckumar · ‎04-07-2022

javax.net.ssl.SSLHandshakeException: Received fatal alert: certificate_required is very generic error for SSL and can cause due to multiple factors such as 1. TLS version mismatch -->TLS version can be changed with StandardSSLContextService 2. Incompatible cipher suites in use by the client and the server --> This can be due to Java version in use by NiFi and Active MQ server and can be checked if there are any specific cipher is set at Active MQ following file needs to be reviewed jre/lib/security/java.security 3. How client certificate obtained and imported in truststore file which is configured under StandardSSLContextService--> You can use SSLPoke to verify connectivity outside of NiFi using same truststore file to makesure if the certificate is fine. Thank you.

ckumar · ‎03-28-2022

Answer to first question: you can use Reporting Task's to get processor status and enrich/trim the information as per you need with in NiFi or you can configure downstream queue for relationship Original from InvokeHTTP procesor and have count on that ,something similar on the lines https://community.cloudera.com/t5/Support-Questions/NiFi-Count-Fileflows-via-attribute/m-p/178860 Answer to Second question : NiFi stores processor related logs under nifi-app.log file which is by default located under /var/log/nifi/ , By default NiFi Processors only prints logs for start and stop operations and Warning and Error associated to the processors , user wont be seeing any events on what is being processed by processor until DEBUG is enabled for Processor class, which is only recommended to use in case of detailed information needed while troubleshooting any problem for short term period. You can filter specific component logs in nifi-app.log by using their component ID. Thank You.

Online	Offline
Last Visited	‎08-05-2026 06:54 AM

Member Since	‎03-10-2017 09:58 AM
Last Visited	‎08-05-2026 06:54 AM
Posts	172
Kudos received	81

Cloudera Community

Re: Data loss(Flow file content) during NIFI Resta...

Re: Schedule Invoking HTTP dynamically - Nifi

Re: Trigger RESTAPI to schedule processors from ni...

Re: Nifi processor missing property

Re: How to consume kafka messages from a specific ...

Re: QueryElasticSearchHTTP does not return anythin...

Re: Nifi authentication fails when a HTTPS load ba...

Re: Nifi setting up ListenFTP - SSL settings

Re: How do you configure a PutMongo NiFi Processor...

Re: Dynamic inputs to Nifi

Re: Can NiFi autoscaling is possible in AWS, how c...

Re: Processor doesn't read saved attribute

Re: Processor doesn't read saved attribute

Re: NIFi : Consume AMQP with SSL StandardSSLContex...

Re: InvokeHTTP - logs for APIs