[
https://issues.apache.org/jira/browse/FLUME-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804660#comment-13804660
]
Dib Ghosh edited comment on FLUME-2220 at 10/24/13 8:54 PM:
------------------------------------------------------------
Hi Rotem,
Correction about the Flume commit process outline I posted in the previous
comment:
----- CORRECTION (last step in the Flume commit process comment above) -----
> Flume committer / contributor reviews the patch; marks it ok to ship; commits
> your patch to appropriate branches in git, in this case I think it should be
> trunk and Flume-1.5 branch in git.
You WON'T be pushing the code from your local branch, someone with committer
privilege can push the code.
was (Author: dib.ghosh):
Hi Rotem,
Correction about the Flume commit process outline I posted in the previous
comment:
****** CORRECTION (last step in the Flume commit process comment above) *******
> Flume committer / contributor reviews the patch; marks it ok to ship; commits
> your patch to appropriate branches in git, in this case I think it should be
> trunk and Flume-1.5 branch in git.
You WON'T be pushing the code from your local branch, someone with committer
privilege can push the code.
> ElasticSearch sink - duplicate fields in indexed document
> ---------------------------------------------------------
>
> Key: FLUME-2220
> URL: https://issues.apache.org/jira/browse/FLUME-2220
> Project: Flume
> Issue Type: Bug
> Affects Versions: v1.4.0
> Reporter: Rotem Hermon
> Priority: Minor
> Labels: ElasticSearch, sink
>
> The default serializer for the ElasticSearch sink
> (ElasticSearchLogStashEventSerializer) duplicates fields that are mapped to
> default logstash fields.
> For instance timestamp, source, host. Those appear both as logstash fields
> ("@timestamp", "@source_host" etc.), and both as fields under the @fields
> ("@fields.timestamp", "@fields.host").
> When inserting a field from the headers as a logstash system field it should
> be removed from the dictionary so it wouldn't get written again under the
> "@fields" field.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
