[
https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15112001#comment-15112001
]
Dave Peterson commented on KAFKA-3088:
--
I wasn't planning on submitting a
[
https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110864#comment-15110864
]
Dave Peterson commented on KAFKA-3088:
--
Ok, gotcha ;-)
Option 1 still s
[
https://issues.apache.org/jira/browse/KAFKA-3088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15110837#comment-15110837
]
Dave Peterson commented on KAFKA-3088:
--
Without being familiar with the code and
Dave Peterson created KAFKA-3088:
Summary: 0.9.0.0 broker crash on receipt of produce request with
empty client ID
Key: KAFKA-3088
URL: https://issues.apache.org/jira/browse/KAFKA-3088
Project: Kafka
I have a broker cluster configured with auto.create.topics.enable=true.
Observing tcpdump output while using kafka-console-producer.sh to
send a message with a previously nonexistent topic, it appears that
the producer instructs the broker to create the topic by sending a
metadata request for that
; messageset). So each
> partition would get its own ack. The response object is just a map of
> partition -> response status so the order of acks in the response is
> the response status map's order.
>
> Joel
>
> On Wed, Jul 23, 2014 at 02:09:40PM -0700, Dave Peterson wro
Hello,
I have a question about produce requests and responses.
Suppose I create a produce request consisting of a single topic T
which contains two message sets S1 and S2, with S1 preceding
S2. In other words, the request looks like this:
( request header ( T ( S1, S2 ) ) )
Is it possible t
Hello, I have a question about produce requests and responses.
I send a produce request containing multiple topics, and get
back a response from the broker containing all topics from the
request. However, the ordering of the topics in the response
differs from the ordering of the topics in the req
Suppose I send a metadata request for a single topic or some small
subset of the entire set of available topics. Will the response contain
broker information for all brokers, or just brokers that contain data for
at least one of the requested topics?
Thanks,
Dave
ioner,
> use it to map the key to a partition id
> 2.3 If a message has a key and the user has not defined a custom
> partitioner, use the default hash based partitioner that ships with Kafka
>
> Thanks,
> Neha
>
>
> On Wed, May 22, 2013 at 1:33 PM, Dave Peterson wrote:
n is done at the producer client. The producer can choose a random
> partition (from the existing list of partitions) or deterministically
> choose a partition based on the key.
>
> Thanks,
>
> Jun
>
>
> On Tue, May 21, 2013 at 1:12 PM, Dave Peterson wrote:
>
>> I
ted through the broker
>> so that a consumer knows what key was used to partition the message on
>> the producer side.
>>
>> I don't believe that you can have the broker decide which partition a
>> message goes to.
>>
>> --
>> Colin B.
>>
>>
1, 2013 at 10:47 AM, Neha Narkhede wrote:
> No. In 0.8, if you don't specify a key for a message, it is sent to any of
> the available partitions. In other words, the partition id is selected on
> the partition and the server doesn't get -1 as the partition id.
>
> Thanks,
In the version 0.8 wire format for a produce request, does a value of -1
still indicate "use a random partition" as it did for 0.7?
Thanks,
Dave
14 matches
Mail list logo
