Bryan, Seems like this is certainly narrow enough in scope that its inclusion would not be anything onerous and would agree that it's a nice fix to include.
On Wed, Aug 26, 2015 at 12:15 PM, Bryan Bende <bbe...@gmail.com> wrote: > All, > > I was testing a scenario this morning using the Flume processors to > leverage > Flume's Syslog sources, and ran into an issue that I created a ticket for > [1]. > > Assuming the patch is reviewed and agreed upon, I would suggest this could > be included in 0.3.0 as it only affects a single line of code in > ExecuteFlumeSource. > If there is any objection to this let me know. > > Thanks, > > Bryan > > [1] https://issues.apache.org/jira/browse/NIFI-895 > > On Wed, Aug 26, 2015 at 10:08 AM, Aldrin Piri <aldrinp...@gmail.com> > wrote: > > > Folks, > > > > I will be acting as the Release Manager for the upcoming 0.3.0 release. > I > > am pleased to announce the tickets that were originally assigned with a > fix > > version of 0.3.0 have been completed and many great features and > > improvements have been incorporated. > > > > Over the past couple of days, some have been doing some in-depth and > > rigorous testing to find and iron out any quirks in using NiFi. This > has, > > so far, generated two issues to be addressed. > > > > Anyone that has a few spare moments and would like to join in, please > feel > > free to do so and identify any unexpected behavior that may arise under > > different scenarios in which you use NiFi or even exceptional cases. > > > > Points of emphasis have been handling system conditions that may arise > due > > to issues concerning disk space and the underlying repositories. > > > > Thanks! > > > > --Aldrin > > >
