[
https://issues.apache.org/jira/browse/FLUME-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13988362#comment-13988362
]
Satoshi Iijima commented on FLUME-2273:
---------------------------------------
I tried above scenario. There is no error and warn in both elasticsearch and
flume and I could get the result by search API not specified indexType.
Using search API specified indexType I got IndexMissingException with 404.
If relative address and '/' of indexName or indexType have the security issue,
this is the problem of elasticsearch not flume.
All - What do you think about it?
> 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)
