Member since
07-30-2019
3397
Posts
1619
Kudos Received
1001
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 428 | 11-05-2025 11:01 AM | |
| 333 | 11-05-2025 08:01 AM | |
| 468 | 11-04-2025 10:16 AM | |
| 685 | 10-20-2025 06:29 AM | |
| 825 | 10-10-2025 08:03 AM |
11-18-2016
05:43 PM
@Toky Raobelina Are the configs provided above from the system you are trying to send data to?
Did you add an "input port" to the root (top level) if the canvas on that server?
So I am gathering you were able to add the RPG, but it is reporting "no input ports available"? Matt
... View more
11-17-2016
11:21 PM
hey @Jobin George, Confirm that G1GC is still set as the garbage collector in your bootstrap.conf. There really isn't much more to this reporting task. How long did you leave it running? Do you have an active dataflow that is constantly using JVM memory? By default this reporting task only runs every 5 minutes. So at the time it runs the threshold would need to be exceeded. Could it be possible that your memory usage is going up and down but overall is low enough to just not trigger? Try running a constant flow of data that is allowed to queue on some connections. Since FlowFile attributes live in memory up to the swap threshold, there would be a constant heap memory usage. See if that does not cause it to trigger. Thanks, Matt
... View more
11-17-2016
10:55 PM
1 Kudo
@Jobin George Are you seeing anything in the nifi-app.log? I configured this reporting task on a instance of HDF 2.0 and it appears to be working. Thank you, Matt
... View more
11-17-2016
07:55 PM
1 Kudo
I would never suggested someone should remove the authorizers.xml file. Both the users.xml and authorizations.xml files are built from the configurations in the authorizers.xml. Did you try providing the absolute paths to your keystore and trustsore jks files in your nifi.properties file?
... View more
11-17-2016
07:37 PM
1 Kudo
@Saikrishna Tarapareddy Are you running your NiFi on Windows or Linux based OS? I do not have a Windows based server available to look at this, but try changing the configurations for path to the keystore and truststore in your nifi.properties file to the fully qualified windows path rather then .\conf\nifidev.truststore.jks Matt
... View more
11-17-2016
06:53 PM
1 Kudo
@Hellmar Becker You may want to try merging your CSV files before sending them to the ConvertCSVtoAvro processor. Try configuring your MergeContent as follows: Feed merged output from this processor to the ConvertCSVtoAvro, then that output to ConvertAvroToORC processor, and finally off to hive. Thanks, Matt
... View more
11-17-2016
06:30 PM
@Hellmar Becker What format are your original messages in before you convert them to Avro?
... View more
11-17-2016
05:29 PM
1 Kudo
@Saikrishna Tarapareddy It seems to not like your users.xml file. Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'authorizer': FactoryBean threw exception on object creation; nested exception is org.apache.nifi.authorization.exception.AuthorizerCreationException: javax.xml.bind.UnmarshalException - with linked exception: [org.xml.sax.SAXParseException; systemId: file:/F:/Tools/HDF-2.0.1.0/nifi/./conf/users.xml; lineNumber: 1; columnNumber: 1; Premature end of file. The users.xml file is created using the values configured in the authorizers.xml file when NiFi is started for the first time after being configured for SSL. Subsequent restarts of NiFi will not result in a new users.xml file being created. This File should not be manually created or edited. Since this is the first time trying to get HTTPS working, try deleting the users.xml and authorizations.xml files and restart again. Do you see the same error still? If so, can you share the configuration from your authorizers.xml file? Thanks, Matt
... View more
11-16-2016
04:03 PM
1 Kudo
Templates when created are not inherently made available to all users. They are tightly coupled to the authorization policies of the process group they are created in. Since these templates are coupled in this way to a particular process group, that process group cannot be deleted until those associated templates are removed. If you access the "templates" UI, you will see a "Process Group Id" column. You should see the process group ID for your "Templates" process group associated with two of your templates. NiFi does not give you the ability to re-associated templates with another existing process group. The idea here is to allow users who are restricted via access policies to some specific process group(s) in NiFi to upload there templates which may contain sensitive configurations and prevent other users from being able to load/use them. Of course a user can adjust the access policies once the template has been uploaded; however, the template remains associated with the Process group in which it was uploaded. Thanks, Matt
... View more
11-15-2016
08:25 PM
Side note: You can install a NiFi 1.x or HDF 2.x and use the flow.xml.gz file from an older 0.5.x+ or HDF 1.1+ version of NiFi. The newer version of NiFi will convert it to the new format.
... View more