Re: Template handling

[Joe Witt]

Hello Uwe,

I agree with your ideas very much and will simply state we have work
to do to fully realize the value that templates can bring.  Take a
look here.  I am happy to add you to the wiki permissions list so you
can update the doc with your thoughts directly.

https://cwiki.apache.org/confluence/display/NIFI/Extension+Registry
https://cwiki.apache.org/confluence/display/NIFI/Variable+Registry
https://cwiki.apache.org/confluence/display/NIFI/Configuration+Management+of+Flows

Thanks
Joe

On Tue, Mar 1, 2016 at 5:39 PM, Uwe Geercken  wrote:
> Hello,
>
> I think working with the templates in nifi is quite good but I have some
> suggestions and would like to hear your comments
>
> - there is no way of saving my flow somehow other than in templates. if I
> create a couple of them, I loose the overview of which template is which. so
> I would recommend to add the time created and the description also to the
> dialog where one selects the template from the dropdown. I know the question
> mark contains the description, but this does not help when there are many
> templates to select from.
> - it would be cool to be able to organize templates in folders (categories)
> - at least if you have many templates
>
> Let me know what you think.
>
> Greetings,
>
> Uwe
>

Template handling

[Uwe Geercken]

Hello,

 

I think working with the templates in nifi is quite good but I have some suggestions and would like to hear your comments

 

- there is no way of saving my flow somehow other than in templates. if I create a couple of them, I loose the overview of which template is which. so I would recommend to add the time created and the description also to the dialog where one selects the template from the dropdown. I know the question mark contains the description, but this does not help when there are many templates to select from.

- it would be cool to be able to organize templates in folders (categories) - at least if you have many templates

 

Let me know what you think.

 

Greetings,

 

Uwe

 

Re: Regular Expressions

[Andy LoPresto]

I use Patterns on OS X. It hasn’t been updated in a few years but it’s done 
everything I need it to.

https://itunes.apple.com/us/app/patterns-the-regex-app/id429449079?mt=12


Andy LoPresto
alopresto.apa...@gmail.com
PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4  BACE 3C6E F65B 2F7D EF69

> On Mar 1, 2016, at 1:30 PM, Uwe Geercken  wrote:
> 
> Hello,
> 
> I was wondering which tool people use to validate their regular expressions?
> 
> I was going throught some of the templates I found in the web and found one 
> with following regular expression:
> 
> (?s:^.*$)
> 
> When using http://www.regexr.com/ which I find very good and complete, 
> regexr.com tells me that the question mark at the beginning is invalid?
> 
> So which way do you write or validate your expressions?
> 
> Tks for feedback.
> 
> Uwe



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: javascript executescript processor

[Mike Harding]

Hi Matt,

That's exactly what I'm looking for - much appreciated !

Thanks,
Mike

On Tue, 1 Mar 2016 at 18:13, Matt Burgess  wrote:

> Mike,
>
> I have a blog containing a few posts on how to use ExecuteScript and
> InvokeScriptedProcessor: http://funnifi.blogspot.com
>
> One contains an example using Javascript to get data from Hazelcast and
> update flowfile attributes:
> http://funnifi.blogspot.com/2016/02/executescript-using-modules.html
>
> If you'd like to share what you'd like to do with ExecuteScript, I'd be
> happy to help you get going!
>
> Regards,
> Matt
>
> On Tue, Mar 1, 2016 at 11:53 AM, Mike Harding 
> wrote:
>
>> Hi,
>>
>> I'd like to utilise the ExecuteScript processor but I understand that its
>> experimental. Can anyone point me in the direction of an example or
>> tutorial preferably using Javascript on how to get started with it?
>>
>> Thanks,
>> Mike
>>
>
>

javascript executescript processor

[Mike Harding]

Hi,

I'd like to utilise the ExecuteScript processor but I understand that its
experimental. Can anyone point me in the direction of an example or
tutorial preferably using Javascript on how to get started with it?

Thanks,
Mike

Re: Disabling Data Provenance

[Andrew Grande]

While not about provenance, but related. One can change log levels for NiFi on 
the fly - edits to the logback.xml file will be reloaded after ~30 seconds 
without the need to restart the instance.

Andrew



On 3/1/16, 3:30 AM, "Shekhar Bansal"  wrote:

>Thanks Joe.
>In our apps, normally we keep log level as info/warn and if we observe
>lots of errors, we change it to debug on the fly.
>I was just wondering if I can do the same with data provenance in NiFi.
>
>Thanks
>Shekhar
>
>On 01/03/16, 12:59 PM, "Joe Witt"  wrote:
>
>>Shekhar
>>
>>You can switch from the default persistent repository to instead use
>>an in-memory only repository.  This can be controlled in the
>>nifi.properties file.  Simply change this
>>
>># Provenance Repository Properties
>>nifi.provenance.repository.implementation=org.apache.nifi.provenance.Persi
>>stentProvenanceRepository
>>
>>...to instead be this
>>
>># Provenance Repository Properties
>>nifi.provenance.repository.implementation=org.apache.nifi.provenance.Volat
>>ileProvenanceRepository
>>
>>At present there is no on-the-fly change for this.  If you have a use
>>case for this would be happy to discuss it.
>>
>>Thanks
>>Joe
>>
>>On Tue, Mar 1, 2016 at 2:23 AM, Shekhar Bansal
>> wrote:
>>> Hi
>>> Can I disable data provenance.
>>> If yes, can I enable disable it on the fly.
>>>
>>> Thanks
>>> Shekhar
>
>

Re: Disabling Data Provenance

[Shekhar Bansal]

Thanks Joe.
In our apps, normally we keep log level as info/warn and if we observe
lots of errors, we change it to debug on the fly.
I was just wondering if I can do the same with data provenance in NiFi.

Thanks
Shekhar

On 01/03/16, 12:59 PM, "Joe Witt"  wrote:

>Shekhar
>
>You can switch from the default persistent repository to instead use
>an in-memory only repository.  This can be controlled in the
>nifi.properties file.  Simply change this
>
># Provenance Repository Properties
>nifi.provenance.repository.implementation=org.apache.nifi.provenance.Persi
>stentProvenanceRepository
>
>...to instead be this
>
># Provenance Repository Properties
>nifi.provenance.repository.implementation=org.apache.nifi.provenance.Volat
>ileProvenanceRepository
>
>At present there is no on-the-fly change for this.  If you have a use
>case for this would be happy to discuss it.
>
>Thanks
>Joe
>
>On Tue, Mar 1, 2016 at 2:23 AM, Shekhar Bansal
> wrote:
>> Hi
>> Can I disable data provenance.
>> If yes, can I enable disable it on the fly.
>>
>> Thanks
>> Shekhar