Re: Suggestion on NIFI UI enhancement

2019-05-07 Thread Otto Fowler
I found this issue already https://issues.apache.org/jira/browse/NIFI-4308.
Maybe you could add your comment to that?

I did not look for 2, I suggest you have a look and create if it doesn’t
exist.


On May 6, 2019 at 20:05:22, Saharan, Naveen (
naveen.kumarsaha...@fmr.com.invalid) wrote:

Hi team,

I have suggestion if the functionality at process group level itself can be
made available from UI:
1. Clear all queues
2. Disable all controller services

Right click over process group and these two options can be made available.
Sometimes its tiresome to clear the queues one by one in big flow.

I know nifi api's are available and we do make use of them while doing any
deployment checking queues are empty and pg is stopped.


Regards,
Naveen
7975363878


[ANNOUNCE] Apache NiFi NAR Maven Plugin 1.3.0 Release

2019-05-07 Thread Bryan Bende
Hello

The Apache NiFi team would like to announce the release of Apache NiFi
nifi-nar-maven-plugin 1.3.0.

Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute data.  Apache NiFi was made for dataflow.  It
supports highly configurable directed graphs of data routing,
transformation, and system mediation logic.

The Apache NiFi NAR Maven Plugin helps to build NiFi Archive bundles
(NARs) to support the class loader isolation model in NiFi.

More details on Apache NiFi can be found here:
https://nifi.apache.org/

Maven artifacts have been made available here:
http://central.maven.org/maven2/org/apache/nifi/nifi-nar-maven-plugin/1.3.0/

Issues closed/resolved for this list can be found here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12340213

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-NiFiNARMavenPluginVersion1.3.0

Thank you,

The Apache NiFi team


Re: [DISCUSS] Release NAR Maven Plugin

2019-05-07 Thread Bryan Bende
While trying to get NiFi master running against the released 1.3.0 NAR
plugin [1], an issue was encountered that can cause the extension
manifest generation to fail [2] . Unfortunately this was hard to
notice unless building with an empty M2 repo.

We'll have to kick out a 1.3.1 shortly. This PR seems to solve the
issue, but will continue to test [3].

[1] https://github.com/apache/nifi/pull/3463
[2] https://issues.apache.org/jira/browse/NIFI-6272
[3] https://github.com/apache/nifi-maven/pull/11

On Mon, Apr 29, 2019 at 10:43 AM Bryan Bende  wrote:
>
> I'll start pulling together the release soon.
>
> On Fri, Apr 26, 2019 at 11:09 AM Joe Witt  wrote:
> >
> > I am also happy for you to take the RM duties :)
> >
> > Thanks Bryan!
> >
> > Joe
> >
> > On Fri, Apr 26, 2019 at 10:54 AM Bryan Bende  wrote:
> >
> > > Hello,
> > >
> > > I'd like to kick out a new release of the NAR Maven plugin soon. The
> > > primary purpose would be for a new feature that generates an extension
> > > descriptor inside each NAR. This descriptor will provide information
> > > to NiFi Registry about what extensions exist in the NAR when version
> > > controlling an extension bundle. For those that are interested, a few
> > > example descriptors are located in the test resources of NiFi Registry
> > > [1].
> > >
> > > Once the NAR plugin is released, we can then bump the version in NiFi
> > > master and start working towards a release of NiFi Registry 0.4.0. I'm
> > > happy to take on RM duties if no one else wants to.
> > >
> > > -Bryan
> > >
> > > [1]
> > > https://github.com/apache/nifi-registry/blob/master/nifi-registry-core/nifi-registry-bundle-utils/src/test/resources/descriptors
> > >


Pull Request Issued

2019-05-07 Thread Ryan Withers
Hello all,

  I think I have finished a jira ticket that was recommended to me, turning
it into a pull request.  You can find out more here:
https://github.com/apache/nifi/pull/3388.

The Jira ticket is here https://issues.apache.org/jira/browse/NIFI-1693 for
continuity.

The gist of the story is to allow properties to honor the standard unix
path expansion to a users home directory.  So a property descriptor dealing
with a file ~/temp.txt would map to /Users/ryanwithers/temp.txt.

I've probably omitted some things.  I'm up to 60 separate occurrences of
the FileExpansionUtil that performs this substitution along with required
tests.  I have achieved a full build of the code base and tested that the
tail file processor will allow for this substitution.

Very interested if I'm honoring the conventions of the community correctly,
including if there is any additional feedback.

Cheers,

Ryan
-- 
Ryan Withers
Senior Software Developer / Analyst

http://www.linkedin.com/in/ryanwithers