Member since
07-30-2019
944
Posts
197
Kudos Received
91
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1787 | 10-05-2021 01:53 PM | |
| 17462 | 09-23-2019 06:03 AM | |
| 7687 | 05-04-2019 08:42 PM |
06-08-2022
12:33 PM
1 Kudo
@_anjos Have you tried setting server.1=node1:2888:3888;2181
... View more
06-08-2022
12:22 PM
@benjbenj I know it has been a while. Have you found a solution for your use case?
... View more
12-29-2021
09:31 AM
@Arash What exactly does the agent flow do? TailFile --> RemoteProcessGroup to NiFi?
... View more
12-29-2021
08:57 AM
@nnndb You are using version JAVA 8 update 11? If so, try using at least JAVA 8 update 252.
... View more
10-05-2021
01:53 PM
@dansteu
There are multiple changes needed in the properties.
The Atlas Configuration Directory shouldn't be on the /tmp directory. The ideal location would be a directory in the default class path of NiFi.
Create Atlas Configuration File should be set to true
If Kerberos is being used for authentication, why is the URL http and not https?
For the NIFi URL for Atlas, it would be better to use http://${hostname(true)}:8080/nifi this will provide a URL that will map back to the NiFi component that generated the Atlas lineage
The Atlas Default Metadata Namespace should be populated with a value that is representative of the flow. For example, For example, hdf352 or testflowversion1, or something similar.
... View more
09-22-2021
07:15 AM
1 Kudo
@dupuy_gregory When using multiple realms, the KDC servers have to have cross-realm trust setup. Here is an article with links to good resources that explain in detail: How does a cross realm trust work? One of the links is broken in the article, here is a good link for the setup of cross-realm trust: Setting up Cross-Realm Kerberos Trusts As a test to make sure it is working, run the kinit command in a terminal window on the NiFi node for the principal in the non-default realm, for example, kinit hdfs-romulus@ROMULUS
... View more
06-26-2020
08:18 AM
2 Kudos
The MiNiFi Java agent builds the nifi.properties file from default values and the ones exposed in the config.yml. To override the default values not exposed in the config.yml, a property must be added to the config.yml in the NiFi Properties Overrides section.
For example, content archiving is disabled by default. To enable this, add the following in the config.yml file:
NiFi Properties Overrides: {
nifi.content.repository.archive.max.retention.period: 1 hour,
nifi.content.repository.archive.max.usage.percentage: 10%,
nifi.content.repository.archive.enabled: 'true'
}
Then, save the config.yml and restart the agent. If you look at the nifi.properties file, you will see the updated values.
NOTE: This is a known issue (internal bug CEM-967) when using the Edge Flow Manager (EFM) to publish flows to the Java agent. When a new flow is published, the agent does not retain the overridden properties. Hence, the properties have to be re-entered manually and then the agent has to be restarted.
... View more
Labels:
01-22-2020
01:45 PM
@ksha The URL looks incorrect: t3://testurl.com:39101. Is the name of the sever where the WebLogic server is running testurl.com? Is the port 39101 correct? The default port for WebLogic is 7001.
... View more
09-23-2019
06:03 AM
@budati If you cannot get the blank space in, then just go back to the default of ; and add it between the parameters in the Command Arguments property.
... View more