You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "Satoshi Iijima (JIRA)" <ji...@apache.org> on 2014/05/01 12:41:17 UTC
[jira] [Commented] (FLUME-2273) ElasticSearchSink: Add handling for
header substitution in indexName
[ https://issues.apache.org/jira/browse/FLUME-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986488#comment-13986488 ]
Satoshi Iijima commented on FLUME-2273:
---------------------------------------
Updated patch.
I add the note of possibility that header substituion can be used for as an attack in doc.
I think this risk should be solved in other ticket if necessary.
> ElasticSearchSink: Add handling for header substitution in indexName
> --------------------------------------------------------------------
>
> Key: FLUME-2273
> URL: https://issues.apache.org/jira/browse/FLUME-2273
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.4.0
> Reporter: Paul Merry
> Priority: Minor
> Attachments: FLUME-2273.patch, new_FLUME-2273-2.patch, new_FLUME-2273-5.patch, new_FLUME-2273.patch
>
>
> The ElasticSearchSink would be improved by allowing for header substitution in the indexName property.
> A use case is where the sink is an intermediate part of a chain and the index name is required to identify the message origin, at present it can only be a hardcoded value.
> The HDFS sink already supports header substitution so a similar format would maintain consistency.
--
This message was sent by Atlassian JIRA
(v6.2#6252)