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
s
> > > 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 be worth thinking
> > > about so
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 :
> Ok, will cook something up by the end of the week
shouldn't refrain from doing them because of
> > of the vote. If we do minor changes after the KIP passes, we usually
> send a
> > follow-up to the vote thread and assume it's all good if no objections
> are
> > raised. Only significant changes require a vote
tition 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 t
1 (binding) - nice API improvement, thanks for driving it!
> > > > >
> > > > > On Mon, Dec 11, 2017 at 11:52 AM Xavier Léauté <
> xav...@confluent.io>
> > > > > wrote:
> > > > >
> > > > > > Thanks Steven, I b
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 even
eady 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, 2017 at
> >
> > > On 8 December 2017 at 18:34, Ted Yu wrote:
> > >
> > >> +1
> > >>
> > >> On Fri, Dec 8, 2017 at 3:49 AM, Steven Aerts
> > >> wrote:
> > >>
> > >> > Hello everybody,
> > >> >
> > &g
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
t'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 wrote:
>
> > Hi Tom,
> >
> > I just made changes to the proposal of KIP-218, to make everything more
>
sted 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 wrote:
>
> > Collin, Ben,
> >
&
t; function);
> >
> > And mark the older declaration as deprecated:
> >
> > > @deprecated
> > > public abstract KafkaFuture thenApply(Function function);
> >
> > This is a 100% compatible way to make things nicer for java 8.
> >
> > cheers,
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 impl
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&focusedCommentId=15867671#comment-15867671
]
Steven Aerts commented on KAFKA-4277:
-
Reproduced on our side with Scala
20 matches
Mail list logo
