[
https://issues.apache.org/jira/browse/FLUME-2225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paweł updated FLUME-2225:
-------------------------
Attachment: FLUME-2225-1.patch
I attach patch-1 which is patch-0 extended by feature to configure rest client.
In configuration of sink there is possibility to configure discoveryFrequency
{code}
a1.sinks.k1.type = elasticsearch
a1.sinks.k1.hostNames = 127.0.0.2:9200
a1.sinks.k1.indexName = foo_index
a1.sinks.k1.indexType = bar_type
a1.sinks.k1.client = rest
a1.sinks.k1.client.discoveryFrequency = 10000
a1.sinks.k1.batchSize = 2
{code}
If discovery frequency (expressed in milliseconds) is grater than 0 rest client
is configured to enable discovery and sets discovery frequency to specified
period of time.
> Elasticsearch Sink for ES HTTP API
> ----------------------------------
>
> Key: FLUME-2225
> URL: https://issues.apache.org/jira/browse/FLUME-2225
> Project: Flume
> Issue Type: New Feature
> Reporter: Otis Gospodnetic
> Fix For: v1.4.1, v1.5.0
>
> Attachments: FLUME-2225-0.patch, FLUME-2225-1.patch
>
>
> Existing ElasticSearchSink uses ES TransportClient. As such, one cannot use
> the ES HTTP API, which is sometimes easier, and doesn't have issues around
> client and server/cluster components using incompatible versions - currently,
> both client and server/cluster need to be on the same version.
> See
> http://search-hadoop.com/m/k76HH9Te68/otis&subj=Elasticsearch+sink+that+uses+HTTP+API
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
