Member since
03-10-2017
171
Posts
80
Kudos Received
32
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1839 | 08-12-2024 08:42 AM | |
| 3020 | 05-30-2024 04:11 AM | |
| 3821 | 05-29-2024 06:58 AM | |
| 2598 | 05-16-2024 05:05 AM | |
| 1950 | 04-23-2024 01:46 AM |
05-16-2022
06:55 AM
1 Kudo
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
... View more
04-25-2022
05:02 AM
Have you tested ListenFTP without setting SSLContextService? just to make sure supplied username and password is correct?
... View more
04-13-2022
06:16 AM
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.
... View more
04-13-2022
05:53 AM
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.
... View more
04-12-2022
07:24 AM
1 Kudo
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.
... View more
04-12-2022
07:06 AM
also, you mentioned "Processor doesn't read saved attribute" Which specific processor you are complaining about ?
... View more
04-12-2022
07:04 AM
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
... View more
04-07-2022
09:17 AM
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.
... View more
03-28-2022
03:49 AM
1 Kudo
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.
... View more
03-14-2022
03:11 AM
1 Kudo
The error seems to be provided from nifi-boostrap.log , please check corresponding nifi-app.log and share for any warning or error leading to stop of nifi service so we can check further and help. Thank You.
... View more