[
https://issues.apache.org/jira/browse/FLUME-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988372#comment-13988372
]
Dipesh Patel commented on FLUME-2273:
-------------------------------------
Hi
I concur with Satoshi. We are heavy users of flume and the elasticsearch sink
and we find that this is an issue with elasticsearch and not really flume.
Indeed if you did not use the sink and posted directly to elasticsearch you
would have the same issue.
Dip
> 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)
