[
https://issues.apache.org/jira/browse/FLUME-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13996346#comment-13996346
]
Deepak Subhramanian commented on FLUME-2273:
--------------------------------------------
If I want to use the patch what are the options to pass in the ESSink
configuration so that it take one of the header field and append in the
indexname.I get JSON and xml data. Since ES automatically parse the JSON data
as an object ,my xml messages are failing as both are created in the same index
and ES validate new messages with the mapping created for JSON object. I like
to have it in the same index. Also I recently noticed that LogstashSerializer
is not generating timestamp fields when I tried to deploy the latest version of
code. It creates two time stamp field with Flume1.4 version.
> 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)
