You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Nikolaos Tsipas (JIRA)" <ji...@apache.org> on 2013/10/25 16:30:31 UTC
[jira] [Commented] (FLUME-2015) ElasticSearchSink: need access to
IndexRequestBuilder instance during flume event processing
[ https://issues.apache.org/jira/browse/FLUME-2015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805342#comment-13805342 ]
Nikolaos Tsipas commented on FLUME-2015:
----------------------------------------
Hello,
I want to be able to set the Ids of documents saved in elasticsearch using flume elasticsearch-sink. This ticket should provide this functionality but I can't find any documentation mentioning how this can be achieved.
Kind Regards,
Nick
> ElasticSearchSink: need access to IndexRequestBuilder instance during flume event processing
> --------------------------------------------------------------------------------------------
>
> Key: FLUME-2015
> URL: https://issues.apache.org/jira/browse/FLUME-2015
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.3.0, v1.3.1
> Reporter: Tim Bacon
> Assignee: Tim Bacon
> Fix For: v1.4.0
>
> Attachments: FLUME-2015-1.4.0-01.patch, FLUME-2015-1.4.0-0.patch, FLUME-2015-1.4.0-1.patch, FLUME-2015-2.patch, FLUME-2015-doc-1.4.0-0.patch
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> I need more control over the indexing performed by the {{ElasticSearchSink}} -- in particular I need access to an {{IndexRequestBuilder}} instance during flume event processing. The interactions between {{ElasticSearchSink}} and {{ElasticSearchEventSerializer}} currently do not make this possible.
> I have authored a patch that meets my needs and maintains backwards-compatibility for existing users of the sink. It is available at [https://github.com/prime8/flume/commit/1056c129b10c95cee50e0c3f77e309668f82bfc6] -- please let me know if it can be pulled into the main ASF source tree!
> Thanks :-)
--
This message was sent by Atlassian JIRA
(v6.1#6144)