+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 <russell.spit...@gmail.com>:

> +1 (non-binding)
>
> On Wed, Jul 18, 2018 at 1:32 AM Marco Gaido <marcogaid...@gmail.com>
> wrote:
>
>> +1 (non-binding)
>>
>>
>> On Wed, 18 Jul 2018, 07:43 Takeshi Yamamuro, <linguin....@gmail.com>
>> wrote:
>>
>>> +1 (non-binding)
>>>
>>> On Wed, Jul 18, 2018 at 2:41 PM John Zhuge <jzh...@apache.org> wrote:
>>>
>>>> +1 (non-binding)
>>>>
>>>> On Tue, Jul 17, 2018 at 8:06 PM Wenchen Fan <cloud0...@gmail.com>
>>>> 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 <b...@apache.org> wrote:
>>>>>
>>>>>> +1 (not binding)
>>>>>>
>>>>>> On Tue, Jul 17, 2018 at 10:59 AM Ryan Blue <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
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Ryan Blue
>>>>>>
>>>>>> --
>>>>>> John Zhuge
>>>>>>
>>>>>
>>>
>>> --
>>> ---
>>> Takeshi Yamamuro
>>>
>>

Reply via email to