ma wrote:
> >
> > > Thanks for the KIP, +1 (binding).
> > >
> > > On 19 Sep 2017 12:27 am, "Richard Yu"
> > wrote:
> > >
> > > > Hello, I would like to start a VOTE thread on KIP-202.
> > > >
> > > > Thanks.
> > > >
> > >
> >
> >
> >
> > --
> > -- Guozhang
> >
>
--
-- Guozhang
; > Thanks for the KIP, +1 (binding).
> >
> > On 19 Sep 2017 12:27 am, "Richard Yu"
> wrote:
> >
> > > Hello, I would like to start a VOTE thread on KIP-202.
> > >
> > > Thanks.
> > >
> >
>
>
>
> --
> -- Guozhang
>
If no on else has opinions or votes on this thread, Richard could you close
the voting phase then?
On Sat, Sep 23, 2017 at 4:11 PM, Ismael Juma wrote:
> Thanks for the KIP, +1 (binding).
>
> On 19 Sep 2017 12:27 am, "Richard Yu" wrote:
>
> > Hello, I would like t
Thanks for the KIP, +1 (binding).
On 19 Sep 2017 12:27 am, "Richard Yu" wrote:
> Hello, I would like to start a VOTE thread on KIP-202.
>
> Thanks.
>
gt;> streams, a warning will be printed (or logged), but this should not
> > >>> hinder
> > >>>> ability to read the log.
> > >>>> There is a missing unchecked warning suppression for the old method.
> > >>>> However, it is not high priority due
>>>> streams, a warning will be printed (or logged), but this should not
> >>> hinder
> >>>> ability to read the log.
> >>>> There is a missing unchecked warning suppression for the old method.
> >>>> However, it is not high prio
t; If we can make it in 1.0.0, I think we can just remove the merge() in
> >>>> StreamsBuilder as it will only be introduced in 1.0.0; if we will add
> >> it
> >>> in
> >>>> 1.1.0, then we indeed need to deprecate it.
> >>>>
> >>>>
>>> If we can make it in 1.0.0, I think we can just remove the merge() in
>>>> StreamsBuilder as it will only be introduced in 1.0.0; if we will add
>> it
>>> in
>>>> 1.1.0, then we indeed need to deprecate it.
>>>>
>>>>
>
o deprecation of the old merge()
>>>> method.
>>>>
>>>>
>>>> On Sun, Sep 17, 2017 at 9:37 AM, Richard Yu <
>> yohan.richard...@gmail.com>
>>>> wrote:
>>>>
>>>>> With regards to Xavier's comment, this pr
to deprecate it.
> > >
> > >
> > > Guozhang
> > >
> > >
> > > On Tue, Sep 19, 2017 at 7:29 AM, Richard Yu <
> yohan.richard...@gmail.com>
> > > wrote:
> > >
> > > > KIP-202 Move merge() from StreamsBuilder to KStream
as it will only be introduced in 1.0.0; if we will add it
> in
> > 1.1.0, then we indeed need to deprecate it.
> >
> >
> > Guozhang
> >
> >
> > On Tue, Sep 19, 2017 at 7:29 AM, Richard Yu
> > wrote:
> >
> > > KIP-202 Move merge()
to deprecate it.
>
>
> Guozhang
>
>
> On Tue, Sep 19, 2017 at 7:29 AM, Richard Yu
> wrote:
>
> > KIP-202 Move merge() from StreamsBuilder to KStream.
> >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> > 202+Move+merge%28%29+from+StreamsBuilder+t
Thanks for the KIP, +1.
If we can make it in 1.0.0, I think we can just remove the merge() in
StreamsBuilder as it will only be introduced in 1.0.0; if we will add it in
1.1.0, then we indeed need to deprecate it.
Guozhang
On Tue, Sep 19, 2017 at 7:29 AM, Richard Yu
wrote:
> KIP-202 M
> > wrote:
> > >
> > >> With regards to Xavier's comment, this practice I do no think applies
> to
> > >> this PR. There is not much potential here for warnings to be thrown.
> > Note
> > >> that in StreamsBuilder's merge, their is no
> > @S
KIP-202 Move merge() from StreamsBuilder to KStream.
https://cwiki.apache.org/confluence/display/KAFKA/KIP-202+Move+merge%28%29+from+StreamsBuilder+to+KStream
This is the link for the VOTE.
On Mon, Sep 18, 2017 at 4:27 PM, Richard Yu
wrote:
> Hello, I would like to start a VOTE thread on
Hello, I would like to start a VOTE thread on KIP-202.
Thanks.
un, Sep 17, 2017 at 9:37 AM, Richard Yu
> > wrote:
> >
> >> With regards to Xavier's comment, this practice I do no think applies to
> >> this PR. There is not much potential here for warnings to be thrown.
> Note
> >> that in StreamsBuilder's merge,
nings is sparse, if not nonexistent.
>>
>>
>> On Sun, Sep 17, 2017 at 9:10 AM, Richard Yu
>> wrote:
>>
>>> KIP-202 has been changed according to the conditions of your suggestion.
>>>
>>> On Sun, Sep 17, 2017 at 8:51 AM, Richard Yu
>>> w
> @SuppressWarnings("unchecked")--indicating
> that warnings is sparse, if not nonexistent.
>
>
> On Sun, Sep 17, 2017 at 9:10 AM, Richard Yu
> wrote:
>
>> KIP-202 has been changed according to the conditions of your suggestion.
>>
>> On Sun, Sep 17, 2017 a
nt.
On Sun, Sep 17, 2017 at 9:10 AM, Richard Yu
wrote:
> KIP-202 has been changed according to the conditions of your suggestion.
>
> On Sun, Sep 17, 2017 at 8:51 AM, Richard Yu
> wrote:
>
>> I added StreamsBuilder under the assumption that InternalStreamBuilder
>> wou
KIP-202 has been changed according to the conditions of your suggestion.
On Sun, Sep 17, 2017 at 8:51 AM, Richard Yu
wrote:
> I added StreamsBuilder under the assumption that InternalStreamBuilder
> would be required to merge
> two streams. However, if that is not the case, then I wo
> -Matthias
>
> On 9/16/17 9:36 PM, Richard Yu wrote:
> > Hi,
> > Please take a look at:
> >
> > https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> > 202+Move+merge%28%29+from+StreamsBuilder+to+KStream
> >
> > Thanks
> >
>
>
e a look at:
>
> https://cwiki.apache.org/confluence/display/KAFKA/KIP-
> 202+Move+merge%28%29+from+StreamsBuilder+to+KStream
>
> Thanks
>
signature.asc
Description: OpenPGP digital signature
Hi,
Please take a look at:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-
202+Move+merge%28%29+from+StreamsBuilder+to+KStream
Thanks
Hi,
Please take a look at:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-202+Move+merge%28%29+from+StreamsBuilder+to+KStream
Thanks
25 matches
Mail list logo
