nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aldrin Piri <aldrinp...@gmail.com>
Subject Re: [DISCUSS] create apache nifi 0.6.1
Date Thu, 31 Mar 2016 15:27:15 GMT
Will take care of it.

On Thu, Mar 31, 2016 at 11:20 AM, Joe Witt <joe.witt@gmail.com> wrote:

> We should also update the downloads page to ensure folks are aware of
> this issue.
>
> I recommend phrasing such as:
> "Before downloading this version please see the release notes [link].
> There is a regression with PutKafka that can cause data loss when
> sending to Kafka.  We will have an 0.6.1 release very soon to address
> that finding."
>
> I can't do it myself right now but if someone else can that would be
> really helpful.
>
> Thanks
> Joe
>
> On Thu, Mar 31, 2016 at 10:57 AM, Oleg Zhurakousky
> <ozhurakousky@hortonworks.com> wrote:
> > +1
> >> On Mar 31, 2016, at 10:54 AM, Joe Witt <joe.witt@gmail.com> wrote:
> >>
> >> I have updated the release notes to reflect that we will produce an
> >> 0.6.1 to correct the PutKafka problem
> >>
> >> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes
> >>
> >> I will start the RM work on this assuming lazy consensus though
> >> clearly there is a good sign of consensus already
> >>
> >> On Thu, Mar 31, 2016 at 10:53 AM, Tony Kurc <trkurc@gmail.com> wrote:
> >>> +1
> >>>
> >>> On Thu, Mar 31, 2016 at 10:44 AM, Mark Payne <markap14@hotmail.com>
> wrote:
> >>>
> >>>> +1 - definitely agree that it warrants a patch release.
> >>>>
> >>>>> On Mar 31, 2016, at 10:29 AM, Joe Witt <joe.witt@gmail.com>
wrote:
> >>>>>
> >>>>> Team,
> >>>>>
> >>>>> I propose that we do an Apache NiFi 0.6.1 release.  There are a
few
> >>>>> important findings we've made and put JIRAs/PRs in for over the
past
> >>>>> couple of days.  The most concerning is that I believe we have a
> >>>>> potential data loss issue introduced in PutKafka.  The general logic
> >>>>> of that processor is far better now but the handling of stream
> >>>>> demarcation is broken.  That is now fixed from NIFI-1701.
> >>>>>
> >>>>> I am happy to RM this if folks are in agreement.
> >>>>>
> >>>>> Thanks
> >>>>> Joe
> >>>>
> >>>>
> >>
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message