Kevin,
Thanks for the reply, I've gone with the password ssh option and its working perfectly.
Thanks
Krish
On 29/07/2018, 16:33 Kevin Doran wrote:
Hi, Glad to hear you are finding the NiFi Registry features useful. Regarding your question, the “Remote Access User” and “Remote Access Password”
Hi Mohit,
>From the log message, I assume that you are using an existing
atlas-application.properties copied from somewhere (most likely from
HDP environment) and PLAINTEXTSASL is used in it.
PLAINTEXTSASL is not supported by the ReportLineageToAtlas.
As a work-around, please set 'Create Atlas Co
Hi Faisai,
Adding ControlRate processor before sending FlowFiles via RPG, you can
throttle the rate of sending data, that should help reducing the
probability for receiving side to get full.
If the current overall throughput is acceptable for your use-case, and
you don't see any data loss, then y
Peter,
They're in separate NARs, and are isolated by different ClassLoaders, so
their state regarding UGI will be separate. There shouldn't be a problem
there. The only way I could think of that might create a problem is if
Atlas JARs were added to HDFS using the Additional Classpath Resources
p
Hi,
Glad to hear you are finding the NiFi Registry features useful. Regarding
your question, the “Remote Access User” and “Remote Access Password”
properties are only used when the remote URL is an HTTPS url. When it is an
SSH url, it is expected that password-less SSH has been configured on you
Hello,
I've just upgraded from NiFi 1.2.0 to 1.7.1 and been playing around with
the NiFi registry features which are great!
I've been trying to get it to push automatically to my bitbucket
repository but I keep getting the following error: "Failed to push
commits to origin due to org.eclipse
