Member since
07-30-2019
3399
Posts
1621
Kudos Received
1001
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 487 | 11-05-2025 11:01 AM | |
| 375 | 11-05-2025 08:01 AM | |
| 606 | 11-04-2025 10:16 AM | |
| 746 | 10-20-2025 06:29 AM | |
| 886 | 10-10-2025 08:03 AM |
12-05-2019
04:49 PM
@emanueol as of this writing, I believe that XML attachments aren't allowed, but you can cut and paste the XML source code into the body of a post using the Insert/edit code sample feature of the editor.
... View more
12-05-2019
12:49 AM
yes, this helped, thank you
... View more
12-04-2019
07:13 AM
@Cl0ck I see nothing you listed as having been removed as an issue. NiFi will create all of the following on startup if they do not exist: - All 4 repository directrories (content, flowfile, database, and provenance) and their contents provided the NiFi service user has permsissions to configured directory to do so. - flow.xml.gz - local state directory and its contents - users.xml (if needed based on authorizers.xml configuration) - authorizations.xml (if needed based on authorizers.xml configuration) I would start by digging in to your shutdown exception: java.lang.IllegalStateException: no valid keystore You'll want to get a verbose listing of your keystore and make sure the following exists: 1. Keystore contains only one PrivateKeyEntry 2. That PrivateKeyEntry has ExtendedKeyUsage (EKU) that supports both clientAuth and ServerAuth 3. That PrivateKeyEntry has one or more SubjectAlternativeName (SAN) entries. One of those SAN entries must match the hostname of the server on which this keystore is being used. 4. The password on the key inside the keystore must use the same password as the keystore itself. A verbose output of your truststore should show that it contains 1 or more TrustedCertEntry Also make sure that your NiFi service users owns and can navigate to the directory where the keystore and truststore files have been placed. Hope this helps, Matt
... View more
12-04-2019
06:23 AM
@pxm You'll want to use the SplitRecord processor to accomplish what you are looking to do. Configure it with a RecordReader and RecordWriter for you input data and desired output data formats along with the desired 1000 records per split. Hope this helps, Matt
... View more
12-02-2019
11:19 AM
Thanks Matt, With new certs, like you mentioned, we were able to make it work.
... View more
11-30-2019
09:48 PM
Any luck getting it working? I'm still working on it to this day, but I think I'm gonna finish it tonight. If so, I can help you when I know my method works.
... View more
11-30-2019
04:27 PM
@MattWho I've been trying these steps and somehow the SAN keeps getting removed when I import/export to JKS. How do I get the SAN extension to be with the key inside of the keystore file? I'm totally stuck!
... View more
11-19-2019
09:46 PM
Any updates to this one, Matt ?
... View more
11-18-2019
11:39 AM
Hi @MattWho We are pursuing cloudera to get a backport of this feature in the current release, as we are unable to upgrade hdf to a version having this feature. Meanwhile I am trying to implement the same using the ExecuteScript(penalize flow file), and eliminate duplicates. When trying to eliminate the duplicates, the detectduplicate does not work as expected when 2 different file names are introduced in the flowfile. Is this expected behaviour? How do we handle this scenario to have unique file list of multiple files over a period of time. The first generateflowfile sets filename as file1.txt and second generateflowfile sets filename as file2.txt. When i disable one of the generateflowfile, it is filtering the duplicates as expected. But when both the generateflowfile are running, we are getting duplicates. Thank you
... View more
11-12-2019
09:35 AM
@vamcits You can use EvaluateJsonPath processor to extract the 0 from the json you shared You can name the custom property added above to whatever you like (I just used C0). This will result in a "C0" attribute being generated on the FlowFile with a value of "[0]". If you don't wan the square brackets around the number, you can remove them using an updateAttribute processor as follows: Then you can perform your routing with the RouteOnAttribute processor. Hope this helps, Matt
... View more