You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Paweł <pr...@gmail.com> on 2014/01/05 20:48:29 UTC
ElasticSearch Sink using HTTP
Hi,
I started preparing Sink for Elasticsearch that uses HTTP API instead of ES
Transport (https://issues.apache.org/jira/browse/FLUME-2225). I decided to
make few modifications in existing Elasticsearch Sink to make it possible
to switch between Transport Client and Http Client. Do you think it is good
way of introducing that feature or should I just make another elasticsearch
sink which will be almost the same as existing one with one difference (it
will use HTTP API).
--
Regards,
Paweł
Re: ElasticSearch Sink using HTTP
Posted by Paweł <pr...@gmail.com>.
Hi,
Thanks for your suggestion about hostname starting with "http". In my
implementation I just added another parameter "client", but "http" before
hostname seems to be even better.
--
Regards,
Paweł
2014/1/5 박치완 <ch...@icloud.com>
> I think ES Sink using HTTP API is very good approach because there is no
> version issue. But instead of new sink implementation, how about adding
> HTTP API feature to sink using ES Transport? (If hostNames start with http
> address, use HTTP API otherwise use ES Transport)
>
> --
> Regards,
> Chiwan Park
>
> On Jan 6, 2014, at 4:48 AM, Paweł <pr...@gmail.com> wrote:
>
> > Hi,
> > I started preparing Sink for Elasticsearch that uses HTTP API instead of
> ES
> > Transport (https://issues.apache.org/jira/browse/FLUME-2225). I decided
> to
> > make few modifications in existing Elasticsearch Sink to make it possible
> > to switch between Transport Client and Http Client. Do you think it is
> good
> > way of introducing that feature or should I just make another
> elasticsearch
> > sink which will be almost the same as existing one with one difference
> (it
> > will use HTTP API).
> >
> > --
> > Regards,
> > Paweł
>
>
Re: ElasticSearch Sink using HTTP
Posted by 박치완 <ch...@icloud.com>.
I think ES Sink using HTTP API is very good approach because there is no
version issue. But instead of new sink implementation, how about adding
HTTP API feature to sink using ES Transport? (If hostNames start with http
address, use HTTP API otherwise use ES Transport)
--
Regards,
Chiwan Park
On Jan 6, 2014, at 4:48 AM, Paweł <pr...@gmail.com> wrote:
> Hi,
> I started preparing Sink for Elasticsearch that uses HTTP API instead of ES
> Transport (https://issues.apache.org/jira/browse/FLUME-2225). I decided to
> make few modifications in existing Elasticsearch Sink to make it possible
> to switch between Transport Client and Http Client. Do you think it is good
> way of introducing that feature or should I just make another elasticsearch
> sink which will be almost the same as existing one with one difference (it
> will use HTTP API).
>
> --
> Regards,
> Paweł