Just to follow up on Matt’s comments, the *name* value is used when the flow is
serialized to the flow.xml.gz file and deserialized. For example, if a property
descriptor has name “ssl-protocol-version” and value “SSL 3.0”, the XML would
look like:
Something using SSLSSL 3.0
…
Now, when
The .name() method is commonly used to provide a more Machine-friendly name, to
help in future Internalization (i18n) efforts. The .displayName() method is
commonly used to provide a user-friendly name. Currently the display name is
used in the UI when present, and if not present, the name is us
On 29 Sep 2017, at 18:50, Giovanni Lanzani wrote:
Now you definitely picked my interest.
I've opened https://issues.apache.org/jira/browse/NIFI-4443 and I'll
try to work on it a bit. I might not tackle the Kerberos stuff just
yet but I'm curious to see if this additional CLASSPATH thingy is
On 29 Sep 2017, at 17:00, Bryan Bende wrote:
Hello,
Unfortunately it isn't really that easy...
The way NiFi is setup you aren't really supposed to be modifying the
classpath, other than adding new NARs to the lib directory.
Each NAR has it's own classloader and isolates the dependencies so
th
Hello,
Unfortunately it isn't really that easy...
The way NiFi is setup you aren't really supposed to be modifying the
classpath, other than adding new NARs to the lib directory.
Each NAR has it's own classloader and isolates the dependencies so
that other NARs don't impact each other, and all N
Hi,
I am trying to append to a Kite Dataset. All is well when I'm using a
local file, but as soon as I try to do it on HDFS on Azure (thus
HDInsight, thus wasb protocol, i.e. Blob Storage) the StoreInKiteDataset
processor is unhappy as the JARs to write using the wasb protocol are
not in the
