[
https://issues.apache.org/jira/browse/FLUME-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483106#comment-13483106
]
Jorn Argelo commented on FLUME-1371:
------------------------------------
As a humble user I'd like to say that it would be great to see this going into
1.3.0. That means I no longer need a rabbitmq or something like that to put
stuff into Elastic Search.
> ElasticSearch Sink
> ------------------
>
> Key: FLUME-1371
> URL: https://issues.apache.org/jira/browse/FLUME-1371
> Project: Flume
> Issue Type: New Feature
> Components: Sinks+Sources
> Affects Versions: v1.3.0
> Reporter: Mubarak Seyed
> Labels: noob
> Attachments: FLUME-1371.patch
>
>
> Motivation:
> Some production usecase(s) requires event(log) to be indexed and searched.
> There are workarounds (e.g. store the log in HDFS and run MapReduce job to
> create an index) but lack of near real-time indexing and search latency are
> concerns for searching the log records.
> Design:
> ElasticSearch supports RESTful style API to publish events for indexing.
> There is an existing ??flumeelastic?? sink [1] in github but it does not
> support batching of events for indexing.
> [1] https://github.com/Aconex/elasticflume
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
