[ 
https://issues.apache.org/jira/browse/FLUME-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13483184#comment-13483184
 ] 

Hari Shreedharan commented on FLUME-1371:
-----------------------------------------

[~brocknoland] - You might need to make some manual changes to poms to make 
sure it commits to all branches without issue.
                
> 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
>             Fix For: v1.3.0
>
>         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

Reply via email to