[
https://issues.apache.org/jira/browse/FLUME-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016213#comment-14016213
]
ASF subversion and git services commented on FLUME-2273:
--------------------------------------------------------
Commit 09472ba12278a0d3696b9d2e26d6d1b0d361c830 in flume's branch
refs/heads/trunk from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=09472ba ]
FLUME-2273 - Add handling for header substitution in ElasticSearchSink
Satoshi Iijima via Juhani Connolly
> 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-6.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)
