[VOTE] FLIP-134: Batch execution for the DataStream API

[Aljoscha Krettek-2]

Hi all,

After the discussion in [1], I would like to open a voting thread for
FLIP-134 (https://s.apache.org/FLIP-134) [2] which discusses a new BATCH
execution mode for the DataStream API.

The vote will be open until September 17, unless there is an objection
or not enough votes.

Regards,
Aljoscha

[1]
https://lists.apache.org/thread.html/reb368f095ec13638b95cd5d885a0aa8e69af06d6e982a5f045f50022%40%3Cdev.flink.apache.org%3E
[2] https://cwiki.apache.org/confluence/x/4i94CQ

[dwysakowicz]

+1 (binding)

On 14/09/2020 14:25, Aljoscha Krettek wrote:

>
> Hi all,
>
> After the discussion in [1], I would like to open a voting thread for
> FLIP-134 (https://s.apache.org/FLIP-134) [2] which discusses a new
> BATCH execution mode for the DataStream API.
>
> The vote will be open until September 17, unless there is an objection
> or not enough votes.
>
> Regards,
> Aljoscha
>
> [1]
> https://lists.apache.org/thread.html/reb368f095ec13638b95cd5d885a0aa8e69af06d6e982a5f045f50022%40%3Cdev.flink.apache.org%3E
> [2] https://cwiki.apache.org/confluence/x/4i94CQ

[Yun Gao]

+1 (non-binding)

Very thanks for bring this up! And the FLIP is indeed necessary for stream & batch unification.

------------------------------------------------------------------
Sender:Dawid Wysakowicz<[hidden email]>
Date:2020/09/16 15:01:08
Recipient:<[hidden email]>; Aljoscha Krettek<[hidden email]>
Theme:Re: [VOTE] FLIP-134: Batch execution for the DataStream API

+1 (binding)

On 14/09/2020 14:25, Aljoscha Krettek wrote:

>
> Hi all,
>
> After the discussion in [1], I would like to open a voting thread for
> FLIP-134 (https://s.apache.org/FLIP-134) [2] which discusses a new
> BATCH execution mode for the DataStream API.
>
> The vote will be open until September 17, unless there is an objection
> or not enough votes.
>
> Regards,
> Aljoscha
>
> [1]
> https://lists.apache.org/thread.html/reb368f095ec13638b95cd5d885a0aa8e69af06d6e982a5f045f50022%40%3Cdev.flink.apache.org%3E
> [2] https://cwiki.apache.org/confluence/x/4i94CQ

[Guowei Ma]

+1 (non-binding)

Best,
Guowei


On Wed, Sep 16, 2020 at 3:03 PM Yun Gao <[hidden email]>
wrote:

> +1 (non-binding)
>
> Very thanks for bring this up! And the FLIP is indeed necessary for stream
> & batch unification.
>
> ------------------------------------------------------------------
> Sender:Dawid Wysakowicz<[hidden email]>
> Date:2020/09/16 15:01:08
> Recipient:<[hidden email]>; Aljoscha Krettek<[hidden email]>
> Theme:Re: [VOTE] FLIP-134: Batch execution for the DataStream API
>
> +1 (binding)
>
> On 14/09/2020 14:25, Aljoscha Krettek wrote:
> >
> > Hi all,
> >
> > After the discussion in [1], I would like to open a voting thread for
> > FLIP-134 (https://s.apache.org/FLIP-134) [2] which discusses a new
> > BATCH execution mode for the DataStream API.
> >
> > The vote will be open until September 17, unless there is an objection
> > or not enough votes.
> >
> > Regards,
> > Aljoscha
> >
> > [1]
> >
> https://lists.apache.org/thread.html/reb368f095ec13638b95cd5d885a0aa8e69af06d6e982a5f045f50022%40%3Cdev.flink.apache.org%3E
> > [2] https://cwiki.apache.org/confluence/x/4i94CQ
>
>
>

[David Anderson-3]

+1

Thanks for the discussion. Looking forward to seeing this all come to pass!

David

On Wed, Sep 16, 2020 at 9:28 AM Guowei Ma <[hidden email]> wrote:

> +1 (non-binding)
>
> Best,
> Guowei
>
>
> On Wed, Sep 16, 2020 at 3:03 PM Yun Gao <[hidden email]>
> wrote:
>
> > +1 (non-binding)
> >
> > Very thanks for bring this up! And the FLIP is indeed necessary for
> stream
> > & batch unification.
> >
> > ------------------------------------------------------------------
> > Sender:Dawid Wysakowicz<[hidden email]>
> > Date:2020/09/16 15:01:08
> > Recipient:<[hidden email]>; Aljoscha Krettek<[hidden email]>
> > Theme:Re: [VOTE] FLIP-134: Batch execution for the DataStream API
> >
> > +1 (binding)
> >
> > On 14/09/2020 14:25, Aljoscha Krettek wrote:
> > >
> > > Hi all,
> > >
> > > After the discussion in [1], I would like to open a voting thread for
> > > FLIP-134 (https://s.apache.org/FLIP-134) [2] which discusses a new
> > > BATCH execution mode for the DataStream API.
> > >
> > > The vote will be open until September 17, unless there is an objection
> > > or not enough votes.
> > >
> > > Regards,
> > > Aljoscha
> > >
> > > [1]
> > >
> >
> https://lists.apache.org/thread.html/reb368f095ec13638b95cd5d885a0aa8e69af06d6e982a5f045f50022%40%3Cdev.flink.apache.org%3E
> > > [2] https://cwiki.apache.org/confluence/x/4i94CQ
> >
> >
> >
>

[Kostas Kloudas-4]

+1

My only suggestion (although by no means a blocker) would be to remove
from the FLIP the `env.setRuntimeMode()` method.
I say that because this is syntactic sugar over the `env.configure()`
with the `execution.runtime-mode` option set to BATCH or STREAMING.
These methods can be nice but they seem to pile up and "pollute" our
user-facing classes. In addition, later on we say that if the user
wants to customize the execution by specifying for example the
shuffle-mode, he/she can only do it through the configuration options.

Apart from that, I agree with the rest of the proposals.

Kostas

On Wed, Sep 16, 2020 at 11:27 AM David Anderson <[hidden email]> wrote:

>
> +1
>
> Thanks for the discussion. Looking forward to seeing this all come to pass!
>
> David
>
> On Wed, Sep 16, 2020 at 9:28 AM Guowei Ma <[hidden email]> wrote:
>
> > +1 (non-binding)
> >
> > Best,
> > Guowei
> >
> >
> > On Wed, Sep 16, 2020 at 3:03 PM Yun Gao <[hidden email]>
> > wrote:
> >
> > > +1 (non-binding)
> > >
> > > Very thanks for bring this up! And the FLIP is indeed necessary for
> > stream
> > > & batch unification.
> > >
> > > ------------------------------------------------------------------
> > > Sender:Dawid Wysakowicz<[hidden email]>
> > > Date:2020/09/16 15:01:08
> > > Recipient:<[hidden email]>; Aljoscha Krettek<[hidden email]>
> > > Theme:Re: [VOTE] FLIP-134: Batch execution for the DataStream API
> > >
> > > +1 (binding)
> > >
> > > On 14/09/2020 14:25, Aljoscha Krettek wrote:
> > > >
> > > > Hi all,
> > > >
> > > > After the discussion in [1], I would like to open a voting thread for
> > > > FLIP-134 (https://s.apache.org/FLIP-134) [2] which discusses a new
> > > > BATCH execution mode for the DataStream API.
> > > >
> > > > The vote will be open until September 17, unless there is an objection
> > > > or not enough votes.
> > > >
> > > > Regards,
> > > > Aljoscha
> > > >
> > > > [1]
> > > >
> > >
> > https://lists.apache.org/thread.html/reb368f095ec13638b95cd5d885a0aa8e69af06d6e982a5f045f50022%40%3Cdev.flink.apache.org%3E
> > > > [2] https://cwiki.apache.org/confluence/x/4i94CQ
> > >
> > >
> > >
> >

[Peter Huang]

+1

Looking forward to the functionality for a long time. With this feature,
our internal users can backfill
data with the same code and minimal change of configuration.

On Fri, Sep 18, 2020 at 3:08 AM Kostas Kloudas <[hidden email]> wrote:

> +1
>
> My only suggestion (although by no means a blocker) would be to remove
> from the FLIP the `env.setRuntimeMode()` method.
> I say that because this is syntactic sugar over the `env.configure()`
> with the `execution.runtime-mode` option set to BATCH or STREAMING.
> These methods can be nice but they seem to pile up and "pollute" our
> user-facing classes. In addition, later on we say that if the user
> wants to customize the execution by specifying for example the
> shuffle-mode, he/she can only do it through the configuration options.
>
> Apart from that, I agree with the rest of the proposals.
>
> Kostas
>
> On Wed, Sep 16, 2020 at 11:27 AM David Anderson <[hidden email]>
> wrote:
> >
> > +1
> >
> > Thanks for the discussion. Looking forward to seeing this all come to
> pass!
> >
> > David
> >
> > On Wed, Sep 16, 2020 at 9:28 AM Guowei Ma <[hidden email]> wrote:
> >
> > > +1 (non-binding)
> > >
> > > Best,
> > > Guowei
> > >
> > >
> > > On Wed, Sep 16, 2020 at 3:03 PM Yun Gao <[hidden email]>
> > > wrote:
> > >
> > > > +1 (non-binding)
> > > >
> > > > Very thanks for bring this up! And the FLIP is indeed necessary for
> > > stream
> > > > & batch unification.
> > > >
> > > > ------------------------------------------------------------------
> > > > Sender:Dawid Wysakowicz<[hidden email]>
> > > > Date:2020/09/16 15:01:08
> > > > Recipient:<[hidden email]>; Aljoscha Krettek<
> [hidden email]>
> > > > Theme:Re: [VOTE] FLIP-134: Batch execution for the DataStream API
> > > >
> > > > +1 (binding)
> > > >
> > > > On 14/09/2020 14:25, Aljoscha Krettek wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > After the discussion in [1], I would like to open a voting thread
> for
> > > > > FLIP-134 (https://s.apache.org/FLIP-134) [2] which discusses a new
> > > > > BATCH execution mode for the DataStream API.
> > > > >
> > > > > The vote will be open until September 17, unless there is an
> objection
> > > > > or not enough votes.
> > > > >
> > > > > Regards,
> > > > > Aljoscha
> > > > >
> > > > > [1]
> > > > >
> > > >
> > >
> https://lists.apache.org/thread.html/reb368f095ec13638b95cd5d885a0aa8e69af06d6e982a5f045f50022%40%3Cdev.flink.apache.org%3E
> > > > > [2] https://cwiki.apache.org/confluence/x/4i94CQ
> > > >
> > > >
> > > >
> > >
>

[Aljoscha Krettek-2]

Hi all,

The voting time for FLIP-134 [1] has passed. I'm closing the vote now.

Including my implicit vote, there were 7 + 1 votes, 4 of which are binding:

- Dawid Wysakowicz (binding)
- Gao Yun
- Ma Guowei
- David Anderson (binding)
- Kostas Kloudas (binding)
- Peter Huang
- Aljoscha Krettek (binding)

There were no -1 votes.

Thus, changes have been accepted. I'll update the FLIP doc accordingly.

[1]
https://cwiki.apache.org/confluence/display/FLINK/FLIP-134%3A+Batch+execution+for+the+DataStream+API

Best,
Aljoscha

On 18.09.20 18:36, Peter Huang wrote:

> +1
>
> Looking forward to the functionality for a long time. With this feature,
> our internal users can backfill
> data with the same code and minimal change of configuration.
>
> On Fri, Sep 18, 2020 at 3:08 AM Kostas Kloudas <[hidden email]> wrote:
>
>> +1
>>
>> My only suggestion (although by no means a blocker) would be to remove
>> from the FLIP the `env.setRuntimeMode()` method.
>> I say that because this is syntactic sugar over the `env.configure()`
>> with the `execution.runtime-mode` option set to BATCH or STREAMING.
>> These methods can be nice but they seem to pile up and "pollute" our
>> user-facing classes. In addition, later on we say that if the user
>> wants to customize the execution by specifying for example the
>> shuffle-mode, he/she can only do it through the configuration options.
>>
>> Apart from that, I agree with the rest of the proposals.
>>
>> Kostas
>>
>> On Wed, Sep 16, 2020 at 11:27 AM David Anderson <[hidden email]>
>> wrote:
>>>
>>> +1
>>>
>>> Thanks for the discussion. Looking forward to seeing this all come to
>> pass!
>>>
>>> David
>>>
>>> On Wed, Sep 16, 2020 at 9:28 AM Guowei Ma <[hidden email]> wrote:
>>>
>>>> +1 (non-binding)
>>>>
>>>> Best,
>>>> Guowei
>>>>
>>>>
>>>> On Wed, Sep 16, 2020 at 3:03 PM Yun Gao <[hidden email]>
>>>> wrote:
>>>>
>>>>> +1 (non-binding)
>>>>>
>>>>> Very thanks for bring this up! And the FLIP is indeed necessary for
>>>> stream
>>>>> & batch unification.
>>>>>
>>>>> ------------------------------------------------------------------
>>>>> Sender:Dawid Wysakowicz<[hidden email]>
>>>>> Date:2020/09/16 15:01:08
>>>>> Recipient:<[hidden email]>; Aljoscha Krettek<
>> [hidden email]>
>>>>> Theme:Re: [VOTE] FLIP-134: Batch execution for the DataStream API
>>>>>
>>>>> +1 (binding)
>>>>>
>>>>> On 14/09/2020 14:25, Aljoscha Krettek wrote:
>>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> After the discussion in [1], I would like to open a voting thread
>> for
>>>>>> FLIP-134 (https://s.apache.org/FLIP-134) [2] which discusses a new
>>>>>> BATCH execution mode for the DataStream API.
>>>>>>
>>>>>> The vote will be open until September 17, unless there is an
>> objection
>>>>>> or not enough votes.
>>>>>>
>>>>>> Regards,
>>>>>> Aljoscha
>>>>>>
>>>>>> [1]
>>>>>>
>>>>>
>>>>
>> https://lists.apache.org/thread.html/reb368f095ec13638b95cd5d885a0aa8e69af06d6e982a5f045f50022%40%3Cdev.flink.apache.org%3E
>>>>>> [2] https://cwiki.apache.org/confluence/x/4i94CQ
>>>>>
>>>>>
>>>>>
>>>>
>>
>