[RESULT] [VOTE] SPIP: Standardize SQL logical plans

[Ryan Blue]

This vote passes with 4 binding +1s and 9 community +1s.

Thanks for taking the time to vote, everyone!

Binding votes:
Wenchen Fan
Xiao Li
Reynold Xin
Felix Cheung

Non-binding votes:
Ryan Blue
John Zhuge
Takeshi Yamamuro
Marco Gaido
Russel Spitzer
Alessandro Solimando
Henry Robinson
Dongjoon Hyun
Bruce Robbins


On Wed, Jul 18, 2018 at 4:43 PM Felix Cheung 
wrote:

> +1
>
>
> --
> *From:* Bruce Robbins 
> *Sent:* Wednesday, July 18, 2018 3:02 PM
> *To:* Ryan Blue
> *Cc:* Spark Dev List
> *Subject:* Re: [VOTE] SPIP: Standardize SQL logical plans
>
> +1 (non-binding)
>
> On Tue, Jul 17, 2018 at 10:59 AM, Ryan Blue  wrote:
>
>> Hi everyone,
>>
>> From discussion on the proposal doc and the discussion thread, I think we
>> have consensus around the plan to standardize logical write operations for
>> DataSourceV2. I would like to call a vote on the proposal.
>>
>> The proposal doc is here: SPIP: Standardize SQL logical plans
>> <https://docs.google.com/document/u/1/d/1gYm5Ji2Mge3QBdOliFV5gSPTKlX4q1DCBXIkiyMv62A/edit?ts=5ace0718&usp=gmail#heading=h.m45webtwxf2d>
>> .
>>
>> This vote is for the plan in that doc. The related SPIP with APIs to
>> create/alter/drop tables will be a separate vote.
>>
>> Please vote in the next 72 hours:
>>
>> [+1]: Spark should adopt the SPIP
>> [-1]: Spark should not adopt the SPIP because . . .
>>
>> Thanks for voting, everyone!
>>
>> --
>> Ryan Blue
>>
>
>

-- 
Ryan Blue

Re: [VOTE] SPIP: Standardize SQL logical plans

[Felix Cheung]

+1



From: Bruce Robbins 
Sent: Wednesday, July 18, 2018 3:02 PM
To: Ryan Blue
Cc: Spark Dev List
Subject: Re: [VOTE] SPIP: Standardize SQL logical plans

+1 (non-binding)

On Tue, Jul 17, 2018 at 10:59 AM, Ryan Blue 
mailto:b...@apache.org>> wrote:
Hi everyone,

>From discussion on the proposal doc and the discussion thread, I think we have 
>consensus around the plan to standardize logical write operations for 
>DataSourceV2. I would like to call a vote on the proposal.

The proposal doc is here: SPIP: Standardize SQL logical 
plans<https://docs.google.com/document/u/1/d/1gYm5Ji2Mge3QBdOliFV5gSPTKlX4q1DCBXIkiyMv62A/edit?ts=5ace0718&usp=gmail#heading=h.m45webtwxf2d>.

This vote is for the plan in that doc. The related SPIP with APIs to 
create/alter/drop tables will be a separate vote.

Please vote in the next 72 hours:

[+1]: Spark should adopt the SPIP
[-1]: Spark should not adopt the SPIP because . . .

Thanks for voting, everyone!

--
Ryan Blue

Re: [VOTE] SPIP: Standardize SQL logical plans

[Bruce Robbins]

+1 (non-binding)

On Tue, Jul 17, 2018 at 10:59 AM, Ryan Blue  wrote:

> Hi everyone,
>
> From discussion on the proposal doc and the discussion thread, I think we
> have consensus around the plan to standardize logical write operations for
> DataSourceV2. I would like to call a vote on the proposal.
>
> The proposal doc is here: SPIP: Standardize SQL logical plans
> 
> .
>
> This vote is for the plan in that doc. The related SPIP with APIs to
> create/alter/drop tables will be a separate vote.
>
> Please vote in the next 72 hours:
>
> [+1]: Spark should adopt the SPIP
> [-1]: Spark should not adopt the SPIP because . . .
>
> Thanks for voting, everyone!
>
> --
> Ryan Blue
>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Dongjoon Hyun]

+1 (non-binding).

Bests,
Dongjoon.

On Wed, Jul 18, 2018 at 11:32 AM Henry Robinson 
wrote:

> +1 (non-binding)
> On Wed, Jul 18, 2018 at 9:12 AM Reynold Xin  wrote:
>
>> +1 on this, on the condition that we can come up with a design that will
>> remove the existing plans.
>>
>>
>> On Tue, Jul 17, 2018 at 11:00 AM Ryan Blue  wrote:
>>
>>> Hi everyone,
>>>
>>> From discussion on the proposal doc and the discussion thread, I think
>>> we have consensus around the plan to standardize logical write operations
>>> for DataSourceV2. I would like to call a vote on the proposal.
>>>
>>> The proposal doc is here: SPIP: Standardize SQL logical plans
>>> 
>>> .
>>>
>>> This vote is for the plan in that doc. The related SPIP with APIs to
>>> create/alter/drop tables will be a separate vote.
>>>
>>> Please vote in the next 72 hours:
>>>
>>> [+1]: Spark should adopt the SPIP
>>> [-1]: Spark should not adopt the SPIP because . . .
>>>
>>> Thanks for voting, everyone!
>>>
>>> --
>>> Ryan Blue
>>>
>>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Henry Robinson]

+1 (non-binding)
On Wed, Jul 18, 2018 at 9:12 AM Reynold Xin  wrote:

> +1 on this, on the condition that we can come up with a design that will
> remove the existing plans.
>
>
> On Tue, Jul 17, 2018 at 11:00 AM Ryan Blue  wrote:
>
>> Hi everyone,
>>
>> From discussion on the proposal doc and the discussion thread, I think we
>> have consensus around the plan to standardize logical write operations for
>> DataSourceV2. I would like to call a vote on the proposal.
>>
>> The proposal doc is here: SPIP: Standardize SQL logical plans
>> 
>> .
>>
>> This vote is for the plan in that doc. The related SPIP with APIs to
>> create/alter/drop tables will be a separate vote.
>>
>> Please vote in the next 72 hours:
>>
>> [+1]: Spark should adopt the SPIP
>> [-1]: Spark should not adopt the SPIP because . . .
>>
>> Thanks for voting, everyone!
>>
>> --
>> Ryan Blue
>>
>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Reynold Xin]

+1 on this, on the condition that we can come up with a design that will
remove the existing plans.


On Tue, Jul 17, 2018 at 11:00 AM Ryan Blue  wrote:

> Hi everyone,
>
> From discussion on the proposal doc and the discussion thread, I think we
> have consensus around the plan to standardize logical write operations for
> DataSourceV2. I would like to call a vote on the proposal.
>
> The proposal doc is here: SPIP: Standardize SQL logical plans
> 
> .
>
> This vote is for the plan in that doc. The related SPIP with APIs to
> create/alter/drop tables will be a separate vote.
>
> Please vote in the next 72 hours:
>
> [+1]: Spark should adopt the SPIP
> [-1]: Spark should not adopt the SPIP because . . .
>
> Thanks for voting, everyone!
>
> --
> Ryan Blue
>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Alessandro Solimando]

+1 (non-binding)

On 18 July 2018 at 17:32, Xiao Li  wrote:

> +1 (binding)
>
> Like what Ryan and I discussed offline, the contents of implementation
> sketch is not part of this vote.
>
> Cheers,
>
> Xiao
>
> 2018-07-18 8:00 GMT-07:00 Russell Spitzer :
>
>> +1 (non-binding)
>>
>> On Wed, Jul 18, 2018 at 1:32 AM Marco Gaido 
>> wrote:
>>
>>> +1 (non-binding)
>>>
>>>
>>> On Wed, 18 Jul 2018, 07:43 Takeshi Yamamuro, 
>>> wrote:
>>>
 +1 (non-binding)

 On Wed, Jul 18, 2018 at 2:41 PM John Zhuge  wrote:

> +1 (non-binding)
>
> On Tue, Jul 17, 2018 at 8:06 PM Wenchen Fan 
> wrote:
>
>> +1 (binding). I think this is more clear to both users and
>> developers, compared to the existing one which only supports
>> append/overwrite and doesn't work with tables in data source(like JDBC
>> table) well.
>>
>> On Wed, Jul 18, 2018 at 2:06 AM Ryan Blue  wrote:
>>
>>> +1 (not binding)
>>>
>>> On Tue, Jul 17, 2018 at 10:59 AM Ryan Blue  wrote:
>>>
 Hi everyone,

 From discussion on the proposal doc and the discussion thread, I
 think we have consensus around the plan to standardize logical write
 operations for DataSourceV2. I would like to call a vote on the 
 proposal.

 The proposal doc is here: SPIP: Standardize SQL logical plans
 
 .

 This vote is for the plan in that doc. The related SPIP with APIs
 to create/alter/drop tables will be a separate vote.

 Please vote in the next 72 hours:

 [+1]: Spark should adopt the SPIP
 [-1]: Spark should not adopt the SPIP because . . .

 Thanks for voting, everyone!

 --
 Ryan Blue

>>>
>>>
>>> --
>>> Ryan Blue
>>>
>>> --
>>> John Zhuge
>>>
>>

 --
 ---
 Takeshi Yamamuro

>>>
>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Xiao Li]

+1 (binding)

Like what Ryan and I discussed offline, the contents of implementation
sketch is not part of this vote.

Cheers,

Xiao

2018-07-18 8:00 GMT-07:00 Russell Spitzer :

> +1 (non-binding)
>
> On Wed, Jul 18, 2018 at 1:32 AM Marco Gaido 
> wrote:
>
>> +1 (non-binding)
>>
>>
>> On Wed, 18 Jul 2018, 07:43 Takeshi Yamamuro, 
>> wrote:
>>
>>> +1 (non-binding)
>>>
>>> On Wed, Jul 18, 2018 at 2:41 PM John Zhuge  wrote:
>>>
 +1 (non-binding)

 On Tue, Jul 17, 2018 at 8:06 PM Wenchen Fan 
 wrote:

> +1 (binding). I think this is more clear to both users and developers,
> compared to the existing one which only supports append/overwrite and
> doesn't work with tables in data source(like JDBC table) well.
>
> On Wed, Jul 18, 2018 at 2:06 AM Ryan Blue  wrote:
>
>> +1 (not binding)
>>
>> On Tue, Jul 17, 2018 at 10:59 AM Ryan Blue  wrote:
>>
>>> Hi everyone,
>>>
>>> From discussion on the proposal doc and the discussion thread, I
>>> think we have consensus around the plan to standardize logical write
>>> operations for DataSourceV2. I would like to call a vote on the 
>>> proposal.
>>>
>>> The proposal doc is here: SPIP: Standardize SQL logical plans
>>> 
>>> .
>>>
>>> This vote is for the plan in that doc. The related SPIP with APIs to
>>> create/alter/drop tables will be a separate vote.
>>>
>>> Please vote in the next 72 hours:
>>>
>>> [+1]: Spark should adopt the SPIP
>>> [-1]: Spark should not adopt the SPIP because . . .
>>>
>>> Thanks for voting, everyone!
>>>
>>> --
>>> Ryan Blue
>>>
>>
>>
>> --
>> Ryan Blue
>>
>> --
>> John Zhuge
>>
>
>>>
>>> --
>>> ---
>>> Takeshi Yamamuro
>>>
>>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Russell Spitzer]

+1 (non-binding)

On Wed, Jul 18, 2018 at 1:32 AM Marco Gaido  wrote:

> +1 (non-binding)
>
>
> On Wed, 18 Jul 2018, 07:43 Takeshi Yamamuro, 
> wrote:
>
>> +1 (non-binding)
>>
>> On Wed, Jul 18, 2018 at 2:41 PM John Zhuge  wrote:
>>
>>> +1 (non-binding)
>>>
>>> On Tue, Jul 17, 2018 at 8:06 PM Wenchen Fan  wrote:
>>>
 +1 (binding). I think this is more clear to both users and developers,
 compared to the existing one which only supports append/overwrite and
 doesn't work with tables in data source(like JDBC table) well.

 On Wed, Jul 18, 2018 at 2:06 AM Ryan Blue  wrote:

> +1 (not binding)
>
> On Tue, Jul 17, 2018 at 10:59 AM Ryan Blue  wrote:
>
>> Hi everyone,
>>
>> From discussion on the proposal doc and the discussion thread, I
>> think we have consensus around the plan to standardize logical write
>> operations for DataSourceV2. I would like to call a vote on the proposal.
>>
>> The proposal doc is here: SPIP: Standardize SQL logical plans
>> 
>> .
>>
>> This vote is for the plan in that doc. The related SPIP with APIs to
>> create/alter/drop tables will be a separate vote.
>>
>> Please vote in the next 72 hours:
>>
>> [+1]: Spark should adopt the SPIP
>> [-1]: Spark should not adopt the SPIP because . . .
>>
>> Thanks for voting, everyone!
>>
>> --
>> Ryan Blue
>>
>
>
> --
> Ryan Blue
>
> --
> John Zhuge
>

>>
>> --
>> ---
>> Takeshi Yamamuro
>>
>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Marco Gaido]

+1 (non-binding)

On Wed, 18 Jul 2018, 07:43 Takeshi Yamamuro,  wrote:

> +1 (non-binding)
>
> On Wed, Jul 18, 2018 at 2:41 PM John Zhuge  wrote:
>
>> +1 (non-binding)
>>
>> On Tue, Jul 17, 2018 at 8:06 PM Wenchen Fan  wrote:
>>
>>> +1 (binding). I think this is more clear to both users and developers,
>>> compared to the existing one which only supports append/overwrite and
>>> doesn't work with tables in data source(like JDBC table) well.
>>>
>>> On Wed, Jul 18, 2018 at 2:06 AM Ryan Blue  wrote:
>>>
 +1 (not binding)

 On Tue, Jul 17, 2018 at 10:59 AM Ryan Blue  wrote:

> Hi everyone,
>
> From discussion on the proposal doc and the discussion thread, I think
> we have consensus around the plan to standardize logical write operations
> for DataSourceV2. I would like to call a vote on the proposal.
>
> The proposal doc is here: SPIP: Standardize SQL logical plans
> 
> .
>
> This vote is for the plan in that doc. The related SPIP with APIs to
> create/alter/drop tables will be a separate vote.
>
> Please vote in the next 72 hours:
>
> [+1]: Spark should adopt the SPIP
> [-1]: Spark should not adopt the SPIP because . . .
>
> Thanks for voting, everyone!
>
> --
> Ryan Blue
>


 --
 Ryan Blue

 --
 John Zhuge

>>>
>
> --
> ---
> Takeshi Yamamuro
>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Takeshi Yamamuro]

+1 (non-binding)

On Wed, Jul 18, 2018 at 2:41 PM John Zhuge  wrote:

> +1 (non-binding)
>
> On Tue, Jul 17, 2018 at 8:06 PM Wenchen Fan  wrote:
>
>> +1 (binding). I think this is more clear to both users and developers,
>> compared to the existing one which only supports append/overwrite and
>> doesn't work with tables in data source(like JDBC table) well.
>>
>> On Wed, Jul 18, 2018 at 2:06 AM Ryan Blue  wrote:
>>
>>> +1 (not binding)
>>>
>>> On Tue, Jul 17, 2018 at 10:59 AM Ryan Blue  wrote:
>>>
 Hi everyone,

 From discussion on the proposal doc and the discussion thread, I think
 we have consensus around the plan to standardize logical write operations
 for DataSourceV2. I would like to call a vote on the proposal.

 The proposal doc is here: SPIP: Standardize SQL logical plans
 
 .

 This vote is for the plan in that doc. The related SPIP with APIs to
 create/alter/drop tables will be a separate vote.

 Please vote in the next 72 hours:

 [+1]: Spark should adopt the SPIP
 [-1]: Spark should not adopt the SPIP because . . .

 Thanks for voting, everyone!

 --
 Ryan Blue

>>>
>>>
>>> --
>>> Ryan Blue
>>>
>>> --
>>> John Zhuge
>>>
>>

-- 
---
Takeshi Yamamuro

Re: [VOTE] SPIP: Standardize SQL logical plans

[John Zhuge]

+1 (non-binding)

On Tue, Jul 17, 2018 at 8:06 PM Wenchen Fan  wrote:

> +1 (binding). I think this is more clear to both users and developers,
> compared to the existing one which only supports append/overwrite and
> doesn't work with tables in data source(like JDBC table) well.
>
> On Wed, Jul 18, 2018 at 2:06 AM Ryan Blue  wrote:
>
>> +1 (not binding)
>>
>> On Tue, Jul 17, 2018 at 10:59 AM Ryan Blue  wrote:
>>
>>> Hi everyone,
>>>
>>> From discussion on the proposal doc and the discussion thread, I think
>>> we have consensus around the plan to standardize logical write operations
>>> for DataSourceV2. I would like to call a vote on the proposal.
>>>
>>> The proposal doc is here: SPIP: Standardize SQL logical plans
>>> 
>>> .
>>>
>>> This vote is for the plan in that doc. The related SPIP with APIs to
>>> create/alter/drop tables will be a separate vote.
>>>
>>> Please vote in the next 72 hours:
>>>
>>> [+1]: Spark should adopt the SPIP
>>> [-1]: Spark should not adopt the SPIP because . . .
>>>
>>> Thanks for voting, everyone!
>>>
>>> --
>>> Ryan Blue
>>>
>>
>>
>> --
>> Ryan Blue
>>
>> --
>> John Zhuge
>>
>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Wenchen Fan]

+1 (binding). I think this is more clear to both users and developers,
compared to the existing one which only supports append/overwrite and
doesn't work with tables in data source(like JDBC table) well.

On Wed, Jul 18, 2018 at 2:06 AM Ryan Blue  wrote:

> +1 (not binding)
>
> On Tue, Jul 17, 2018 at 10:59 AM Ryan Blue  wrote:
>
>> Hi everyone,
>>
>> From discussion on the proposal doc and the discussion thread, I think we
>> have consensus around the plan to standardize logical write operations for
>> DataSourceV2. I would like to call a vote on the proposal.
>>
>> The proposal doc is here: SPIP: Standardize SQL logical plans
>> 
>> .
>>
>> This vote is for the plan in that doc. The related SPIP with APIs to
>> create/alter/drop tables will be a separate vote.
>>
>> Please vote in the next 72 hours:
>>
>> [+1]: Spark should adopt the SPIP
>> [-1]: Spark should not adopt the SPIP because . . .
>>
>> Thanks for voting, everyone!
>>
>> --
>> Ryan Blue
>>
>
>
> --
> Ryan Blue
>

Re: [VOTE] SPIP: Standardize SQL logical plans

[Ryan Blue]

+1 (not binding)

On Tue, Jul 17, 2018 at 10:59 AM Ryan Blue  wrote:

> Hi everyone,
>
> From discussion on the proposal doc and the discussion thread, I think we
> have consensus around the plan to standardize logical write operations for
> DataSourceV2. I would like to call a vote on the proposal.
>
> The proposal doc is here: SPIP: Standardize SQL logical plans
> 
> .
>
> This vote is for the plan in that doc. The related SPIP with APIs to
> create/alter/drop tables will be a separate vote.
>
> Please vote in the next 72 hours:
>
> [+1]: Spark should adopt the SPIP
> [-1]: Spark should not adopt the SPIP because . . .
>
> Thanks for voting, everyone!
>
> --
> Ryan Blue
>


-- 
Ryan Blue

[VOTE] SPIP: Standardize SQL logical plans

[Ryan Blue]

Hi everyone,

>From discussion on the proposal doc and the discussion thread, I think we
have consensus around the plan to standardize logical write operations for
DataSourceV2. I would like to call a vote on the proposal.

The proposal doc is here: SPIP: Standardize SQL logical plans

.

This vote is for the plan in that doc. The related SPIP with APIs to
create/alter/drop tables will be a separate vote.

Please vote in the next 72 hours:

[+1]: Spark should adopt the SPIP
[-1]: Spark should not adopt the SPIP because . . .

Thanks for voting, everyone!

-- 
Ryan Blue