Proposal: add nifi-elasticsearch-5-nar to a profile build in nifi-assembly

[Mike Thomsen <mi...@gmail.com>]

This bundle uses the "Transport API" and that is almost done being phased
out as a public client API in Elasticsearch as of 7.X, IIRC.

It would also free up 34MB from the convenience binary.

Thoughts?

Re: Proposal: add nifi-elasticsearch-5-nar to a profile build in nifi-assembly

[Joe Witt <jo...@gmail.com>]

I'm supportive of es5 bits moving into a profile and not being included by
default.  Space savings for the older things is good where usage isn't
known to be huge.

Thanks

On Wed, Jul 1, 2020 at 3:24 PM Mike Thomsen <mi...@gmail.com> wrote:

> Matt,
>
> I don't think it's an either-or, but we should work on making the
> nifi-elasticsearch-restapi-processors package the future-proof one since it
> uses the official Elastic Java clients and has more features in certain
> areas like it's able to use the JSON DSL.
>
> The main reason I'm proposing moving the v5 package out is because it is
> essentially version specific with no real future ahead of it.
>
> Thanks,
>
> Mike
>
> On Wed, Jul 1, 2020 at 12:49 PM Matt Burgess <ma...@apache.org> wrote:
>
> > Mike,
> >
> > I like the idea, but should we fix the known issues with the ESHttp
> > processors for ES 7 first? Not to say that those are keeping folks
> > from upgrading from ES 5 to 7, just saying we might be well served for
> > now with a bundle that seems pretty stable. I'm not married to the
> > notion though, if others agree we should move the ES5 stuff into a
> > profile, I'm on board :)
> >
> > Regards,
> > Matt
> >
> > On Mon, Jun 29, 2020 at 2:54 PM Mike Thomsen <mi...@gmail.com>
> > wrote:
> > >
> > > This bundle uses the "Transport API" and that is almost done being
> phased
> > > out as a public client API in Elasticsearch as of 7.X, IIRC.
> > >
> > > It would also free up 34MB from the convenience binary.
> > >
> > > Thoughts?
> >
>

Re: Proposal: add nifi-elasticsearch-5-nar to a profile build in nifi-assembly

[Mike Thomsen <mi...@gmail.com>]

Matt,

I don't think it's an either-or, but we should work on making the
nifi-elasticsearch-restapi-processors package the future-proof one since it
uses the official Elastic Java clients and has more features in certain
areas like it's able to use the JSON DSL.

The main reason I'm proposing moving the v5 package out is because it is
essentially version specific with no real future ahead of it.

Thanks,

Mike

On Wed, Jul 1, 2020 at 12:49 PM Matt Burgess <ma...@apache.org> wrote:

> Mike,
>
> I like the idea, but should we fix the known issues with the ESHttp
> processors for ES 7 first? Not to say that those are keeping folks
> from upgrading from ES 5 to 7, just saying we might be well served for
> now with a bundle that seems pretty stable. I'm not married to the
> notion though, if others agree we should move the ES5 stuff into a
> profile, I'm on board :)
>
> Regards,
> Matt
>
> On Mon, Jun 29, 2020 at 2:54 PM Mike Thomsen <mi...@gmail.com>
> wrote:
> >
> > This bundle uses the "Transport API" and that is almost done being phased
> > out as a public client API in Elasticsearch as of 7.X, IIRC.
> >
> > It would also free up 34MB from the convenience binary.
> >
> > Thoughts?
>

Re: Proposal: add nifi-elasticsearch-5-nar to a profile build in nifi-assembly

[Matt Burgess <ma...@apache.org>]

Mike,

I like the idea, but should we fix the known issues with the ESHttp
processors for ES 7 first? Not to say that those are keeping folks
from upgrading from ES 5 to 7, just saying we might be well served for
now with a bundle that seems pretty stable. I'm not married to the
notion though, if others agree we should move the ES5 stuff into a
profile, I'm on board :)

Regards,
Matt

On Mon, Jun 29, 2020 at 2:54 PM Mike Thomsen <mi...@gmail.com> wrote:
>
> This bundle uses the "Transport API" and that is almost done being phased
> out as a public client API in Elasticsearch as of 7.X, IIRC.
>
> It would also free up 34MB from the convenience binary.
>
> Thoughts?