Hi,
This is to know more about Kafka and how i can use it in my project. I am
trying to learn about Big Data Engineering and came across Kafka. I am
trying to develop an application which could take some real time data,
filter it and show some visual outputs and would like to know where Kafka
could
>> I have a feeling that it would be helpful to add this to documentation
>> examples as well as javadocs for all methods that do return iterators.
That makes sense. Can you create a JIRA for this? Thanks.
-Matthias
On 9/27/17 2:54 PM, Stas Chizhov wrote:
> Thanks, that comment actually mad its
Thanks, that comment actually mad its way to the documentation already.
Apparently none of that was related. It was a leak - I was not closing an
iterator that was returned by
https://kafka.apache.org/0110/javadoc/org/apache/kafka/streams/state/ReadOnlyWindowStore.html#fetch(K,%20long,%20long)
Meth
Have you seen this comment ?
https://issues.apache.org/jira/browse/KAFKA-5122?focusedCommentId=15984467&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15984467
On Wed, Sep 27, 2017 at 12:44 PM, Stas Chizhov wrote:
> Hi,
>
> I am running a simple kafka streams app
Hi,
I am running a simple kafka streams app (0.11.0.1) that counts messages per
hour per partition. The app runs in a docker container with a memory limit
set, which is always reached by the app within few minutes and then
container is killed. After running it with various number of instances,
dif
All connectors are compatible with vanilla AK, as Confluent Open Source
ships with "plain" Apache Kafka under the hood.
So you can just download the connector, plug it in, and configure it as
any other connector, too.
https://www.confluent.io/product/connectors/
-Matthias
On 9/26/17 1:15 PM, M
An OutOfOrderSequenceException should only occur if a idempotent
producer gets out of sync with the broker. If you set
`enable.idempotence = true` on your producer, you might want to set
`retries = Integer.MAX_VALUE`.
-Matthias
On 9/26/17 11:30 PM, Sameer Kumar wrote:
> Hi,
>
> I again received
I understand that it won't support it, my only concern is about the error
code.
Locally with these settings I get a message formatted error, 43 . Which
makes sense.
In one particular cluster we see an invalid request 42 instead of
unsupported format 43.
What are the implications of changing the
The 0.8.1 protocol does not support target timestamps so it makes sense
that you would get an invalid request error if the client is sending a
Version 1 or Version 2 Offsets Request. The only Offset Request that a
0.8.1 broker knows how to handle is a Version 0 Offsets Request.
>From https://kafka
Correction in above mail, we get 42 - INVALID_REQUEST, not 43.
Few other data points
Server has following configs set
inter.broker.protocol.version=0.8.1
log.message.format.version=0.8.1
My understanding is that we should get unsupported message format with
above configurations, why do we get
Hi,
We are using LibrdKafka library version .11.0 and calling List Offset API
with a timestamp on a 0.10.2 kafka server installed in a windows machine.
This request returns an error code, 43 - INVALID_REQUEST.
We have other local installations of Kafka version 0.10.2 (also on Windows)
and are ab
I'm not sure how much helpful it will be for you, but there was a talk
about "Best practices for running Kafka on Docker" on the Kafka Summit in
August. You can check the video and slides here: https://www.confluent.io/
kafka-summit-sf17/resource/
Jakub
On Tue, Sep 26, 2017 at 6:56 AM, Anoop Putt
Hi Roshan,
KafkaStreams apps run as a client application. It does not run on the
broker. You develop an application and give it an `application.id` - you
deploy how over many instances of that application you like and they all
share the same topology. I suggest you take a look at the docs here:
ht
13 matches
Mail list logo
