Member since
06-26-2015
515
Posts
137
Kudos Received
114
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
2094 | 09-20-2022 03:33 PM | |
5736 | 09-19-2022 04:47 PM | |
3104 | 09-11-2022 05:01 PM | |
3444 | 09-06-2022 02:23 PM | |
5442 | 09-06-2022 04:30 AM |
02-24-2022
06:26 PM
I'm not sure if it's possible run SFTP commands other than put/get in NiFi. Sorry, André
... View more
02-24-2022
06:21 PM
Hi, @rahulsingh710 , Sorry, but I've run out of ideas. This is really weird and I'm not sure what the problem is. If you have a Cloudera support subscription, I'd suggest you open a case with them, if you already haven't done so. Cheers, André
... View more
02-24-2022
06:06 PM
Hi @Aditya-Moghe , Could you please share the exact steps you took to install and start NiFi? André
... View more
02-24-2022
06:02 PM
@Ane , You can specify the database as part of the JDBC URI you pass to beeline. For example: beeline -u "jdbc:hive2://<hostname>:10000/<dbname>" HTH, André
... View more
02-24-2022
06:00 PM
Hi, @spserd , Interesting what you mentioned below: Flink 1.8.0 with NiFi artifacts (org.apache.nifi) in 1.11.6 - SUCCESS case Flink 1.14.3 with NiFi artifacts (org.apache.nifi) in 1.15.3 - FAILED case You upgraded Flink *and* NiFi versions at once. I don't think the Flink version would make a difference, but there's been some security changes in NiFi 1.15. I'm not sure how those would affect your case, but there's a possibility that they could require some additional configuration. The 401 error (authentication error) seen in your logs is probably related to the anonymous login. The anonymous login indicates to me that there's something wrong with your keystore. Are you able to share the keystore and truststore details I asked before? It's also weird that you had to add the truststore contents to the default Java cacerts. You should not need to do that if the truststore was being passed correctly to the job. Are you running your job in cluster mode? Is that on YARN? Wherever that job is running you must ensure that the keystore and truststore are available for the job to read them, at the right location. Could you please also share the command line that you use to submit the job? Cheers, André
... View more
02-24-2022
02:06 AM
Looking at the full list of nodes, do you see any nodes where the sum of the memory used and memory available is different from 231GB?
... View more
02-24-2022
02:00 AM
@wert_1311 , Would you be able to share the stack traces from the application logs? André
... View more
02-24-2022
01:58 AM
Hi @Aditya-Moghe , The setup still works in the same way. The only difference is that TLS and authentication are turned on by default for NiFi in the latest version. After you unpack and start the NiFi service, you can now access it through the following URL: https://<hostname>:8443/nifi/ You can find the generated username and password by grepping the NiFi log. For example: ❯ grep "Generated [PU]" logs/nifi-app.log
Generated Username [e4d1972e-88b5-43f1-af15-5b4a54f706c5]
Generated Password [n7G7x9ud+2WjQR6aESrnxrjdi6sgqzl+] Cheers, André
... View more
02-24-2022
01:48 AM
Hi, @STK , Your user probably has been granted two policies: The global "view the user interface" policy, which you can access via the Policies menu: The "Modify component" policy that you configure for the root "NiFi Flow" process group component: Your user is probably missing the "view the component" policy for the NiFi Flow process group: Try granting this and see if it resolves your problem. Regards, André
... View more