[
https://issues.apache.org/jira/browse/FLUME-2220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13804506#comment-13804506
]
Dib Ghosh commented on FLUME-2220:
----------------------------------
Hi Rotem,
My apologies for misinterpreting your bug post. I also started on Flume commit
process very recently.
> Typically, you start off with assigning the ticket to yourself.
> Make changes in your local flume copy
> Test the changes
> Create diff file of the patch once you have tested the changes
> Goto https://reviews.apache.org, upload the diff file, tag the bug with JIRA
> and the group to Flume
> Upload the patch to the JIRA ticket and mark the ticket as patch-available
> Once someone reviews the patch and marks it ok to ship commit your patch to
> appropriate branches in git, in this case I think it should be trunk and
> Flume-1.5 branch in git
You can find more details here
(https://cwiki.apache.org/confluence/display/FLUME/Developers+Quick+Hack+Sheet)
and here (https://cwiki.apache.org/confluence/display/FLUME/How+to+Contribute).
Hope this helps,
- Dib
> 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)
