[ 
https://issues.apache.org/jira/browse/FLUME-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15563041#comment-15563041
 ] 

ASF subversion and git services commented on FLUME-2999:
--------------------------------------------------------

Commit 585c4c92ed65c529871765ab64a5b3637fbdb07d in flume's branch 
refs/heads/trunk from [~tmgstev]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=585c4c9 ]

FLUME-2999. Kafka channel and sink should enable statically assigned partition 
per event via header

This feature is useful for anyone who needs greater control of which
partitions are being written to - normally in a situation where multiple
Flume agents are being deployed in order to horizontally scale, or
alternatively if there is a scenario where there is a skew in data that
might lead to one or more partitions hotspotting.

We also have the ability to specify custom partitions on to the Kafka
Producer itself using the kafka.* configuration properties. The Kafka
Producer provides the ability to set the partition ID using a particular
ProducerRecord constructor, this is just a matter of providing the
option to use this constructor.

Reviewers: Attila Simon, Mike Percy

(Tristan Stevens via Mike Percy)


> Kafka channel and sink should enable statically assigned partition per event 
> via header
> ---------------------------------------------------------------------------------------
>
>                 Key: FLUME-2999
>                 URL: https://issues.apache.org/jira/browse/FLUME-2999
>             Project: Flume
>          Issue Type: Improvement
>          Components: Channel, Sinks+Sources
>    Affects Versions: v1.7.0
>            Reporter: Tristan Stevens
>            Assignee: Tristan Stevens
>            Priority: Minor
>             Fix For: v1.7.0
>
>
> This feature is useful for anyone who needs greater control of which 
> partitions are being written to - normally in a situation where multiple 
> Flume agents are being deployed in order to horizontally scale, or 
> alternatively if there is a scenario where there is a skew in data that might 
> lead to one or more partitions hotspotting.
> We also have the ability to specify custom partitions on to the Kafka 
> Producer itself using the kafka.* configuration properties.
> The Kafka Producer provides the ability to set the partition ID using the 
> following constructor 
> (https://kafka.apache.org/090/javadoc/org/apache/kafka/clients/producer/ProducerRecord.html#ProducerRecord(java.lang.String,%20java.lang.Integer,%20K,%20V%29
>  ), this is just a matter of providing the option to use this constructor.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to