James,
I'm not certain what Joe intends here, as it works for me.
I've used it in NiFi 1.1.1 and have notes on it (just today, actually
<http://www.javahotchocolate.com/notes/nifi.html#20170324>) for my guys
to use, however, my example uses two processors you don't have, a way to
create an arbitrary flowfile and a no-op processor (could have been any
processor only stopped).
Better than my notes is this nice how-to by Yolanda from last September:
https://community.hortonworks.com/articles/57304/supporting-custom-properties-for-expression-langua.html
Hope this helps,
Russ
On 03/24/2017 11:07 AM, Joe Witt wrote:
We made our initial capability available but we still have more work
to go to reach the full vision of that feature proposal/vision as well
as related visions for extensions and flow versions.
On Fri, Mar 24, 2017 at 1:02 PM, Matt Foley <[email protected]> wrote:
Hi Joe,
The specification document in the wiki is written in future tense, but is it in
fact what got implemented in the two jiras (all linked below)?
Thanks,
--Matt
On 3/24/17, 5:50 AM, "Joe Witt" <[email protected]> wrote:
James,
In NiFi 1.x line we introduced the variable registry concept for
exactly this purpose. Right now it reads from a properties file but we
intend to also grow this to support other more dynamic/central
options.
https://issues.apache.org/jira/browse/NIFI-2208
https://issues.apache.org/jira/browse/NIFI-2449
https://cwiki.apache.org/confluence/display/NIFI/Variable+Registry
Thanks
JOe
On Fri, Mar 24, 2017 at 8:47 AM, James McMahon <[email protected]>
wrote:
> I would like to allow my workflow administrators to control NiFi
attribute
> and configuration parameters using an editable configuration text file
read
> in at start up - similar to nifi.properties. How can I do this?
>
> An example would be the hostname and port for our AMQP broker, or for
> HandleHttpRequest. -Jim
