nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anshuman Ghosh <anshuman.ghosh2...@gmail.com>
Subject Re: whats new in nifi 1.2.0 / careful use of marks and being clear about non released features
Date Fri, 28 Apr 2017 14:28:02 GMT
Thank you Bryan, it will be very helpful :-)
Have a great weekend!

‚Äč
______________________

*Kind Regards,*
*Anshuman Ghosh*
*Contact - +49 179 9090964*


On Fri, Apr 28, 2017 at 4:15 PM, Bryan Bende <bbende@gmail.com> wrote:

> Anshuman,
>
> You shouldn't have to download anything to use the NiFI NAR Maven Plugin.
>
> If you are building the latest NiFi code on the master branch then it
> will already be using version 1.2.0:
>
> https://github.com/apache/nifi/blob/master/pom.xml#L1780
>
> If you are building your own NARs then you just need to update the
> version wherever you declare the plugin.
>
> In either case, Maven will fetch the plugin from Maven central.
>
> Thanks,
>
> Bryan
>
>
> On Fri, Apr 28, 2017 at 10:06 AM, Anshuman Ghosh
> <anshuman.ghosh2009@gmail.com> wrote:
> > Hello Andre,
> >
> > Thank you so much for the reply!
> > Yes we are excited about the Schema Registry also :-)
> > As per the release note "NiFi NAR Maven Plugin Version 1.2.0" was
> supposed
> > to release by March 17, 2017
> > I do not find that here though - https://nifi.apache.org/download.html
> >
> > Any idea how to merge this.
> > Thanking you in advance!
> >
> >
> > ______________________
> >
> > *Kind Regards,*
> > *Anshuman Ghosh*
> > *Contact - +49 179 9090964*
> >
> >
> > On Fri, Apr 28, 2017 at 3:19 PM, Andre <andre-lists@fucs.org> wrote:
> >
> >> Anshuman,
> >>
> >> The GCS processors have been merged to master a few weeks ago so in my
> >> personal opinion it should be a fairly safe bet to assume they will
> make to
> >> 1.2.0. Emphasis on assume. :-)
> >>
> >> From what I gather the code base is reaching stability and as per email
> >> from Bryan earlier this week we should soon see the RC leaving the oven.
> >>
> >> Not sure if looked at the merge history lately and I certainly don't
> want
> >> to set high expectations.... But the changes since 1.1.2 are looking
> >> amazing... Like... Truly amazing.
> >>
> >> But as I said, don't want to set high expectations so hold tight as
> Bryan
> >> continues to roast the RC.
> >>
> >> Cheers
> >>
> >>
> >>
> >> On Fri, Apr 28, 2017 at 11:01 PM, Anshuman Ghosh <
> >> anshuman.ghosh2009@gmail.com> wrote:
> >>
> >> > Hello Joe,
> >> >
> >> > I was about to write an email to the community and just then I have
> >> > received this email. Thank you!
> >> >
> >> > I would like to know whether GCS processors are available or not?
> >> > We have a requirement to use them.
> >> > From where I get this latest version as the one we have downloaded
> >> doesn't
> >> > seem to have GCS processors.
> >> >
> >> > Thanking you in advance!
> >> >
> >> >
> >> > ______________________
> >> >
> >> > *Kind Regards,*
> >> > *Anshuman Ghosh*
> >> > *Contact - +49 179 9090964*
> >> >
> >> >
> >> > On Fri, Apr 28, 2017 at 2:45 PM, Joe Witt <joe.witt@gmail.com> wrote:
> >> >
> >> > > Team,
> >> > >
> >> > > Just noticed these slides
> >> > > https://www.slideshare.net/KojiKawamura/whats-newnifi120
> >> > >
> >> > > While the deck itself seems quite solid and does cover a lot of
> really
> >> > > important materials we must be very careful in presenting such
> >> > > materials before the release is an officially PMC voted upon
> artifact.
> >> > >
> >> > > The note on the description is good "Summarizes new capabilities
> added
> >> > > to Apache NiFi 1.2.0 (soon to be released)." but the slides
> themselves
> >> > > need to adhere to the naming guidelines and need to make it very
> clear
> >> > > that the features/fixes/etc.. being described are not released and
> >> > > subject to change.
> >> > >
> >> > > The first use of naming should always call out the proper full name
> >> > > which would be Apache NiFi.
> >> > >
> >> > > Thanks
> >> > > Joe
> >> > >
> >> >
> >>
>

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