Gabor Somogyi created KAFKA-10318:
-
Summary: Default API timeout must be enforced to be greater than
request timeout just like in AdminClient
Key: KAFKA-10318
URL: https://issues.apache.org/jira/browse/KAFKA
+1 (non-binding) I've had a deeper look and this would be a good addition
to Spark.
On Thu, Aug 15, 2019 at 6:19 PM Viktor Somogyi-Vass
wrote:
> Started to implement my proposition and thought about it a little bit more
> and it seems like I overthought the problem and we'd actually be better o
Gabor Somogyi created KAFKA-8809:
Summary: Infinite retry if secure cluster tried to be reached from
non-secure consumer
Key: KAFKA-8809
URL: https://issues.apache.org/jira/browse/KAFKA-8809
Project
+1 (non-binding)
I've read it through in depth and as Jungtaek said Spark can make good use
of it.
On Wed, 14 Aug 2019, 17:06 Jungtaek Lim, wrote:
> +1 (non-binding)
>
> I found it very useful for Spark's case. (Discussion on KIP-505 described
> it.)
>
> Thanks for driving the effort!
>
> 2019년
I've had a look on KIP-396 and until now only 1 binding vote arrived. Hope
others would consider it as a good solution...
G
On Tue, Aug 13, 2019 at 11:52 AM Gabor Somogyi
wrote:
> I've had concerns calling AdminClient.listTopics because on big clusters
> I've seen OO
t;> partitions and
> >> > > >> adopt the changes or validate the expectation. That's not only
> use
> >> case
> >> > > for
> >> > > >> poll(0). Spark is also seeking the offset per topicpartition to
> the
> >
usly, relying on listener to hear
> > the news on reassignment. Unfortunately that's not the case.
> >
> > Unit tests in Spark have similar needs: looks like Kafka test code also
> > leverages `updateAssignmentMetadataIfNeeded` and `poll(0)` in many places
> >
Hi Guys,
Please see the actual implementation, pretty sure it explains the situation
well:
https://github.com/apache/spark/blob/master/external/kafka-0-10-sql/src/main/scala/org/apache/spark/sql/kafka010/KafkaOffsetReader.scala
To answer one question/assumption which popped up from all of you Spa
nClient#describeTopics for that. If you want to create the topics,
> you
> >> could use AdminClient#createTopics.
> >>
> >> best,
> >> Colin
> >>
> >>
> >> On Fri, Aug 9, 2019, at 11:23, Gabor Somogyi wrote:
> >>
> Each KafkaConsumer method that returns metadata will already block until
such metadata is available
The old API was waiting infinitely but the new has a timeout which has
effect on the metadata fetch as well.
Spark is interested in only the assigned partitions and/or
latest/earliest/... offsets.
Gabor Somogyi created KAFKA-8468:
Summary: AdminClient.deleteTopics doesn't wait until topic is
deleted
Key: KAFKA-8468
URL: https://issues.apache.org/jira/browse/KAFKA-8468
Project:
Gabor Somogyi created KAFKA-8234:
Summary: Multi-module support for JAAS config property
Key: KAFKA-8234
URL: https://issues.apache.org/jira/browse/KAFKA-8234
Project: Kafka
Issue Type
Gabor Somogyi created KAFKA-8128:
Summary: Dynamic delegation token change possibility for
consumer/producer
Key: KAFKA-8128
URL: https://issues.apache.org/jira/browse/KAFKA-8128
Project: Kafka
Gabor Somogyi created KAFKA-7927:
Summary: Read committed receives aborted events
Key: KAFKA-7927
URL: https://issues.apache.org/jira/browse/KAFKA-7927
Project: Kafka
Issue Type: Bug
Gabor Somogyi created KAFKA-7677:
Summary: Client login with already existing JVM subject
Key: KAFKA-7677
URL: https://issues.apache.org/jira/browse/KAFKA-7677
Project: Kafka
Issue Type: New
15 matches
Mail list logo
