Member since
06-26-2015
515
Posts
140
Kudos Received
114
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2586 | 09-20-2022 03:33 PM | |
| 6986 | 09-19-2022 04:47 PM | |
| 3688 | 09-11-2022 05:01 PM | |
| 4304 | 09-06-2022 02:23 PM | |
| 6814 | 09-06-2022 04:30 AM |
03-15-2022
03:34 AM
1 Kudo
Hi , @krishna123, Thanks for the output! This explains the issue that you're seeing. You mentioned before that you were using Java 1.8.0_275, but the log line you just provided shows that NiFi is actually using Java 1.8.0_74. In this version of Java, cryptographic key sizes are limited and NiFi cannot not handle AES keys larger than 128 bits. Because of that, NiFi fails to instantiate AES iphers properly. To enable that in your Java version, you would have to download the Java Cryptography Extension (JCE) Unlimited Strength policies and copy them to your Java home manually to allow AES keys of size 256 and larger. These policies are only included by default in the JDK starting from update 1.8.0_162. If you already have Java 1.8.0_275 installed, make sure NiFi can see it and use it. This will solve your problem. You can verify which Java version NiFi is using by checking the line that I mentioned in the log. Cheers, André -- 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.
... View more
03-15-2022
02:16 AM
Could you please look into your nifi-bootstrap.conf and look for the line like the one below and paste it here? 2022-03-15 16:03:24,008 INFO [main] org.apache.nifi.bootstrap.RunNiFi Runtime Java version: ...
... View more
03-14-2022
11:14 PM
@krishna123 , Could you please provide the full stack trace of the exception you found in nifi-app.log? André
... View more
03-14-2022
10:10 PM
@krishna123 , What's the exact version? (java -version) Cheers, André
... View more
03-14-2022
10:08 PM
Hi @gaofzhan, For what reason are you copying the JDBC driver to the NiFi's lib folder? When you need to JDBC driver for connecting to the remote sources, you typically only need to copy the ojdbc8.jar file. If you copy all the files that come in the tarball downloaded from Oracle it can cause errors like the one you describe. Please remove the copied files from the lib folder, copy only the ojdbc8.jar one and try again. Cheers, André -- 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.
... View more
03-14-2022
07:38 PM
1 Kudo
Hi, @VikasNayak07 , An easy way to achieve this is to use a JoltTransformRecord processor with a JsonTreeReader and a CSVRecordSetWriter. The following "Chain" transformation will produce the output that you want: [
{
"operation": "shift",
"spec": {
"tokens": {
"*": "[&].token"
}
}
}
] Cheers, André -- 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.
... View more
03-14-2022
07:14 PM
Hi, @Onkar_Gagre , You can use a Record Path expression to do what you want in a QueryRecord processor. Please try the example below: SELECT *
FROM FLOWFILE
WHERE RPATH(labels, '/site_identifier') = 'xyz' Cheers, André -- 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.
... View more
03-14-2022
06:39 PM
Yep, I know. Would you be able to share the content of that file? You can send it to me in pvt if you prefer. André
... View more
03-14-2022
03:48 PM
@gaofzhan , What's the exact JDBC driver and version that you added to the lib folder? André
... View more