Steven Aerts created KAFKA-7635:
---
Summary: FetcherThread stops processing after "Error processing
data for partition"
Key: KAFKA-7635
URL: https://issues.apache.org/jira/browse/KAFKA-7635
ove points
> has
> > > alternatives (or compromises) which might make the problem more
> > tractable,
> > > so I'd welcome hearing from anyone who has ideas on that. In particular
> > > there are parallels with consumer offsets which might b
Xavier, Ismael,
I think I updated everything.
The KIP has been lined up with the latest version of the PR, it is free for
everyone to be reviewed.
Thanks for your feedback,
Steven
Op do 18 jan. 2018 om 13:10 schreef Steven Aerts <steven.ae...@gmail.com>:
> Ok, will cook som
s require a vote from scratch (this tends
> to
> > be rare). More inline.
> >
> > On Tue, Dec 19, 2017 at 7:58 PM, Steven Aerts <steven.ae...@gmail.com>
> > wrote:
> > >
> > > > 1. The KIP seems to rely on the pull request for some of the details
rtition if we could reassure
> ourselves it would scale OK to the reassignment sizes would people need in
> practice.
>
> Overall I would prefer not to tackle something like this in *this* KIP,
> though it could be something for a future KIP. Of course I'm happy to hear
> more
Hello Ismael.
Thanks for you feedback.
> 1. The KIP seems to rely on the pull request for some of the details of the
> proposal. Generally, the KIP should stand on its own.
Looking back at what I wrote in the KIP, I agree that its style is too
descriptive
and relies too much on the content of
12:40 PM, Gwen Shapira <g...@confluent.io>
> > > wrote:
> > > >
> > > > > +1 (binding) - nice API improvement, thanks for driving it!
> > > > >
> > > > > On Mon, Dec 11, 2017 at 11:52 AM Xavier Léauté <
> xav...@confluent.io>
Tom,
I think it would be useful to be able to subscribe yourself on updates of
reassignment changes.
Our internal kafka supervisor and monitoring tools are currently subscribed
to these changes in zookeeper so they can babysit our clusters.
I think it would be nice if we could receive these
. Since you already have a PR out, it might be worth
> > incorporating
> > my fixes (and the extra docs), what do you think?
> >
> > I'll rebase my PR onto yours to make it easier to merge.
> >
> > Thanks!
> > Xavier
> >
> >
> > On Mon, Dec 4
lt;t.j.bent...@gmail.com>
> wrote:
> > > +1
> > >
> > > On 8 December 2017 at 18:34, Ted Yu <yuzhih...@gmail.com> wrote:
> > >
> > >> +1
> > >>
> > >> On Fri, Dec 8, 2017 at 3:49 AM, Steven Aerts <steve
Hello everybody,
I think KIP-218 is crystallized enough to start voting.
KIP documentation:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-218%3A+Make+KafkaFuture.Function+java+8+lambda+compatible
Thanks,
Steven
main thing that's
> missing for my work in KIP-183 is that addWaiter() needs to be public.
>
> Thanks again,
>
> Tom
>
> On 2 December 2017 at 10:07, Steven Aerts <steven.ae...@gmail.com> wrote:
>
> > Hi Tom,
> >
> > I just made changes to the prop
'm particularly interested in seeing progress on this KIP as the work for
> KIP-183 needs a public version of BiConsumer. do you have any idea when the
> KIP might be ready for voting?
>
> Thanks,
>
> Tom
>
> On 10 November 2017 at 13:38, Steven Aerts <steven.ae...@gmail.com
ract KafkaFuture thenApply(FunctionInterface<T, R>
> > function);
> >
> > And mark the older declaration as deprecated:
> >
> > > @deprecated
> > > public abstract KafkaFuture thenApply(Function<T, R> function);
> >
> > This is a 1
Hi Tom,
Nice observation.
I changed "Rejected Alternatives" section to "Other Alternatives", as
I see myself as too much of an outsider to the kafka community to be
able to decide without this discussion.
I see two major factors to decide:
- how soon will KIP-118 (drop support of java 7) be
Hey everybody,
I made a KIP to improve working with the KafkaFuture class from java 8.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-218%3A+Make+KafkaFuture.Function+java+8+lambda+compatible
All comments are more than welcome.
Thanks,
Steven
I hereby would like to request write access to the wiki to create a
KIP for KAFKA-6018.
My wiki id is steven.aerts.
Thanks,
Steven
GitHub user steven-aerts opened a pull request:
https://github.com/apache/kafka/pull/4033
KAFKA-6018: Make KafkaFuture.Future an interface
Changing KafkaFuture.Future and KafkaFuture.BiConsumer into an interface
makes
them a functional interface. This makes them Java 8 lambda
Steven Aerts created KAFKA-6018:
---
Summary: Make from KafkaFuture.Function java 8 lambda compatible
Key: KAFKA-6018
URL: https://issues.apache.org/jira/browse/KAFKA-6018
Project: Kafka
Issue
[
https://issues.apache.org/jira/browse/KAFKA-4277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15867671#comment-15867671
]
Steven Aerts commented on KAFKA-4277:
-
Reproduced on our side with Scala 2.11 kafka_2.11-0.10.1.1
20 matches
Mail list logo
