Mailing-List: contact users-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@nifi.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAEwabr7_5D=5dvF_e55O9CPzCv-aChRs4BCyi4-_XF7P9UinJA@mail.gmail.com>
References: 
 <CAEwabr68jGjTH1=PWjxgRM=o684a5f-5387ZW42Babm-35gkDw@mail.gmail.com>
	<678440313.2845936.1457107230136.JavaMail.yahoo@mail.yahoo.com>
	<CAC9dF2dwrnqCd1dXgBUi+3ExAnFT+Oe=+8ZjszwFZYjLEJvZvA@mail.gmail.com>
	<trinity-19b0f118-482f-4a27-bcaf-155c335bbb11-1457115745237@3capp-webde-bs03>
	<CALJK9a7uQ39C0K5NMxO5=UwrjsHP6yPvO1Dph9L1cdQ_yZ1N4Q@mail.gmail.com>
	<CAEwabr7_5D=5dvF_e55O9CPzCv-aChRs4BCyi4-_XF7P9UinJA@mail.gmail.com>
Date: Fri, 4 Mar 2016 13:57:31 -0500
Message-ID: 
 <CALJK9a51sVi63iW1RG7QMHomP86LbU+f1eo+k2Up6g6ToHy0xA@mail.gmail.com>
Subject: Re: Re: List Files
From: Joe Witt <joe.witt@gmail.com>
To: users@nifi.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Charlie,

Yeah you're right that is a viable option now too.  And we support
environment variables from the system too.  So for things that support
expression language that helps.

The variable registry obviously will give us a nice step forward.

Thanks
Joe

On Fri, Mar 4, 2016 at 1:55 PM, Charlie Frasure
<charliefrasure@gmail.com> wrote:
> Thanks Joe,
>
> That option is certainly more comprehensive than what I was looking to do=
.
> An UpdateAttribute at the beginning of a flow (or even before a process
> group) could establish the variables I need.  One case that either
> UpdateAttribute or the Variable Registry should consider is being able to
> mark sensitive properties so that things like passwords can remain secure=
.
>
>
> On Fri, Mar 4, 2016 at 1:24 PM, Joe Witt <joe.witt@gmail.com> wrote:
>>
>> No.  But we need to and plan to
>> https://cwiki.apache.org/confluence/display/NIFI/Variable+Registry
>>
>> On Fri, Mar 4, 2016 at 1:22 PM, Uwe Geercken <uwe.geercken@web.de> wrote=
:
>> > Matthew,
>> >
>> > does NiFi itself allow to define such things as constants? The idea
>> > would be
>> > to re-use these constants (e.g. a path) in different processors.
>> >
>> > Rgds,
>> >
>> > Uwe
>> >
>> > Gesendet: Freitag, 04. M=C3=A4rz 2016 um 19:04 Uhr
>> > Von: "Matthew Clarke" <matt.clarke.138@gmail.com>
>> > An: users@nifi.apache.org, "Joe Percivall" <joepercivall@yahoo.com>
>> > Betreff: Re: List Files
>> >
>> > The expression language can also be used to return values from both JV=
M
>> > properties set in the NiFi bootstrap.conf and system environment
>> > variables
>> > for the user running NiFi.
>> >
>> > On Mar 4, 2016 11:00 AM, "Joe Percivall" <joepercivall@yahoo.com> wrot=
e:
>> >>
>> >> Hello,
>> >>
>> >> ListFile is a source processor so this behavior is expected. It
>> >> supports
>> >> expression language so that it can be configured to utilize certains
>> >> methods. For example, some people may want to get a list of files fro=
m
>> >> a
>> >> rotating directory that gets created every hour. To do that they woul=
d
>> >> need
>> >> to use the date functions included in Expression Language.
>> >>
>> >> Does forbidding input hinder a specific use-case you have?
>> >>
>> >> Joe
>> >>
>> >> - - - - - -
>> >> Joseph Percivall
>> >> linkedin.com/in/Percivall
>> >> e: joepercivall@yahoo.com
>> >>
>> >>
>> >>
>> >> On Friday, March 4, 2016 10:38 AM, Charlie Frasure
>> >> <charliefrasure@gmail.com> wrote:
>> >>
>> >>
>> >>
>> >> I'm using the 0.5.1 build and having what I think is odd behavior for
>> >> ListFile.  The processor supports expression language in the Input
>> >> Directory
>> >> property, however I can't figure out how to configure an attribute as
>> >> input.
>> >>
>> >> I tried using UpdateAttribute prior to ListFile, but ListFile doesn't
>> >> seem
>> >> to allow incoming connections.  I also tried creating an attribute
>> >> within
>> >> ListFile, but it doesn't seem to be available for referencing within
>> >> the
>> >> same processor.
>> >>
>> >> Is this expected?  If so, what is the intended purpose of allowing
>> >> expression language in this attribute?
>
>