[
https://issues.apache.org/jira/browse/FLUME-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14173422#comment-14173422
]
Hudson commented on FLUME-2499:
-------------------------------
SUCCESS: Integrated in Flume-trunk-hbase-98 #37 (See
[https://builds.apache.org/job/Flume-trunk-hbase-98/37/])
FLUME-2499. Include Kafka Message Key in Event Headers. (hshreedharan:
http://git-wip-us.apache.org/repos/asf/flume/repo?p=flume.git&a=commit&h=622faa6f8812cd751dfad22deaa21bf0aa613111)
*
flume-ng-sources/flume-kafka-source/src/main/java/org/apache/flume/source/kafka/KafkaSource.java
*
flume-ng-sources/flume-kafka-source/src/main/java/org/apache/flume/source/kafka/KafkaSourceConstants.java
> Include Kafka Message Key in Event Header, Updated Comments
> ------------------------------------------------------------
>
> Key: FLUME-2499
> URL: https://issues.apache.org/jira/browse/FLUME-2499
> Project: Flume
> Issue Type: Improvement
> Components: Sinks+Sources
> Affects Versions: v1.5.0.1
> Reporter: Ricky Saltzer
> Assignee: Ricky Saltzer
> Priority: Minor
> Attachments: FLUME-2499.diff, FLUME-2499.diff
>
>
> I believe it would be useful to include a message's key in the event header,
> as users will often want to partition based on this key when ingesting into a
> sink.
> *Example:*
> {code}
> sfdc.sinks.hdfs.hdfs.path =
> /data/testing/kafka_flume/dataset=%{key}/year=%Y/month=%m/day=%d/
> {code}
> In this case, the first part of the partition key is the Kafka message key,
> which will ensure messages are organized by key.
> I also updated some of the comments and cleaned up the code slightly.
> Cheers,
> Ricky
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
