KAFKA-6144(or other ticket to resolve)

[Nikolay Izhikov <ni...@apache.org>]

Hello, Kafka developers.

I found the link to a KAFKA-6144 in youtube video [1]
Gwen, Matthias, great video by the way :)

I want to know - is this ticket actual for the Kafka product?

Are commiters and other community members are interested in it's resolve?

It unassigned for now and I want to work on it.
Can I expect that some commiters help me with it?

May be you can offer some other ticket to me, that has to be resolved?

I'm experienced java programmer with 1 KIP done and a couple commits in Kafka trunk :)

[1] https://www.youtube.com/watch?v=TG77-nNR1yw

Re: KAFKA-6144(or other ticket to resolve)

[Nikolay Izhikov <ni...@apache.org>]

Hello, Matthias.

> it's a complex beast and we need to lay out a sound design.

Thats, what I looking for :)

> If this does (hopefully) not scare you, feel free to pick it up.

Yes, I want to pick it up.
After, KAFKA-7420 which is almost done and KAFKA-6970 I start working on
this ticket.

> IMHO, we should tackle the issue holistically and thus first discuss:

Thank you for this questions list.
I start working on this ticket from this list.

> How does this sound?

This sounds great.
Thank you for a detailed answer!


вт, 4 дек. 2018 г. в 20:32, Matthias J. Sax <ma...@confluent.io>:

> Thanks Nikolay,
>
> of course we would like to get this ticket resolved! Just a heads up:
> it's a complex beast and we need to lay out a sound design. Thus, I
> expect a long KIP discussion. If this does (hopefully) not scare you,
> feel free to pick it up.
>
> Also note, related https://issues.apache.org/jira/browse/KAFKA-6555 (and
> the corresponding PR) -- please also sync with Ashish (comment on the
> Jira) if he is still interested in working on this. He got silent for a
> while, so maybe not, but we should double check.
>
> IMHO, we should tackle the issue holistically and thus first discuss:
>
>  - Do we want to allow to query state active stores?
>  - Do we want to allow to query Standby stores?
>  - What are the pros/cons for both approaches?
>  - Could it make sense to support both?
>  - If we support both, can we design/implement them independent or do we
> need one holistic design?
>  - Do we need user facing API changes?
>  - Is this feature enabled by default, or do users need to opt-in?
>
> And maybe others. Thus, a good starting point might be to write up a KIP
> that covers all those questions, and proposes desired semantics and how
> developers would use this feature. As a second step, we can think about
> implementation details.
>
> How does this sound?
>
>
> -Matthias
>
> On 12/3/18 11:27 PM, Nikolay Izhikov wrote:
> > Hello, Kafka developers.
> >
> > I found the link to a KAFKA-6144 in youtube video [1]
> > Gwen, Matthias, great video by the way :)
> >
> > I want to know - is this ticket actual for the Kafka product?
> >
> > Are commiters and other community members are interested in it's resolve?
> >
> > It unassigned for now and I want to work on it.
> > Can I expect that some commiters help me with it?
> >
> > May be you can offer some other ticket to me, that has to be resolved?
> >
> > I'm experienced java programmer with 1 KIP done and a couple commits in
> Kafka trunk :)
> >
> > [1] https://www.youtube.com/watch?v=TG77-nNR1yw
> >
>
>

Re: KAFKA-6144(or other ticket to resolve)

["Matthias J. Sax" <ma...@confluent.io>]

Thanks Nikolay,

of course we would like to get this ticket resolved! Just a heads up:
it's a complex beast and we need to lay out a sound design. Thus, I
expect a long KIP discussion. If this does (hopefully) not scare you,
feel free to pick it up.

Also note, related https://issues.apache.org/jira/browse/KAFKA-6555 (and
the corresponding PR) -- please also sync with Ashish (comment on the
Jira) if he is still interested in working on this. He got silent for a
while, so maybe not, but we should double check.

IMHO, we should tackle the issue holistically and thus first discuss:

 - Do we want to allow to query state active stores?
 - Do we want to allow to query Standby stores?
 - What are the pros/cons for both approaches?
 - Could it make sense to support both?
 - If we support both, can we design/implement them independent or do we
need one holistic design?
 - Do we need user facing API changes?
 - Is this feature enabled by default, or do users need to opt-in?

And maybe others. Thus, a good starting point might be to write up a KIP
that covers all those questions, and proposes desired semantics and how
developers would use this feature. As a second step, we can think about
implementation details.

How does this sound?


-Matthias

On 12/3/18 11:27 PM, Nikolay Izhikov wrote:
> Hello, Kafka developers.
> 
> I found the link to a KAFKA-6144 in youtube video [1]
> Gwen, Matthias, great video by the way :)
> 
> I want to know - is this ticket actual for the Kafka product?
> 
> Are commiters and other community members are interested in it's resolve?
> 
> It unassigned for now and I want to work on it.
> Can I expect that some commiters help me with it?
> 
> May be you can offer some other ticket to me, that has to be resolved?
> 
> I'm experienced java programmer with 1 KIP done and a couple commits in Kafka trunk :)
> 
> [1] https://www.youtube.com/watch?v=TG77-nNR1yw
>