+1 (non binding)


   view my Linkedin profile
<https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/>



*Disclaimer:* Use it at your own risk. Any and all responsibility for any
loss, damage or destruction of data or any other property which may arise
from relying on this email's technical content is explicitly disclaimed.
The author will in no case be liable for any monetary damages arising from
such loss, damage or destruction.




On Tue, 16 Nov 2021 at 15:28, Gengliang Wang <[email protected]> wrote:

> +1 (non-binding)
>
> On Tue, Nov 16, 2021 at 9:03 PM Wenchen Fan <[email protected]> wrote:
>
>> +1
>>
>> On Mon, Nov 15, 2021 at 2:54 AM John Zhuge <[email protected]> wrote:
>>
>>> +1 (non-binding)
>>>
>>> On Sun, Nov 14, 2021 at 10:33 AM Chao Sun <[email protected]> wrote:
>>>
>>>> +1 (non-binding). Thanks Anton for the work!
>>>>
>>>> On Sun, Nov 14, 2021 at 10:01 AM Ryan Blue <[email protected]> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> Thanks to Anton for all this great work!
>>>>>
>>>>> On Sat, Nov 13, 2021 at 8:24 AM Mich Talebzadeh <
>>>>> [email protected]> wrote:
>>>>>
>>>>>> +1 non-binding
>>>>>>
>>>>>>
>>>>>>
>>>>>>    view my Linkedin profile
>>>>>> <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/>
>>>>>>
>>>>>>
>>>>>>
>>>>>> *Disclaimer:* Use it at your own risk. Any and all responsibility
>>>>>> for any loss, damage or destruction of data or any other property which 
>>>>>> may
>>>>>> arise from relying on this email's technical content is explicitly
>>>>>> disclaimed. The author will in no case be liable for any monetary damages
>>>>>> arising from such loss, damage or destruction.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Sat, 13 Nov 2021 at 15:07, Russell Spitzer <
>>>>>> [email protected]> wrote:
>>>>>>
>>>>>>> +1 (never binding)
>>>>>>>
>>>>>>> On Sat, Nov 13, 2021 at 1:10 AM Dongjoon Hyun <
>>>>>>> [email protected]> wrote:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> On Fri, Nov 12, 2021 at 6:58 PM huaxin gao <[email protected]>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> +1
>>>>>>>>>
>>>>>>>>> On Fri, Nov 12, 2021 at 6:44 PM Yufei Gu
>>>>>>>>> <[email protected]> wrote:
>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> > On Nov 12, 2021, at 6:25 PM, L. C. Hsieh <[email protected]>
>>>>>>>>>> wrote:
>>>>>>>>>> >
>>>>>>>>>> > Hi all,
>>>>>>>>>> >
>>>>>>>>>> > I’d like to start a vote for SPIP: Row-level operations in Data
>>>>>>>>>> Source V2.
>>>>>>>>>> >
>>>>>>>>>> > The proposal is to add support for executing row-level
>>>>>>>>>> operations
>>>>>>>>>> > such as DELETE, UPDATE, MERGE for v2 tables (SPARK-35801). The
>>>>>>>>>> > execution should be the same across data sources and the best
>>>>>>>>>> way to do
>>>>>>>>>> > that is to implement it in Spark.
>>>>>>>>>> >
>>>>>>>>>> > Right now, Spark can only parse and to some extent analyze
>>>>>>>>>> DELETE, UPDATE,
>>>>>>>>>> > MERGE commands. Data sources that support row-level changes
>>>>>>>>>> have to build
>>>>>>>>>> > custom Spark extensions to execute such statements. The goal of
>>>>>>>>>> this effort
>>>>>>>>>> > is to come up with a flexible and easy-to-use API that will
>>>>>>>>>> work across
>>>>>>>>>> > data sources.
>>>>>>>>>> >
>>>>>>>>>> > Please also refer to:
>>>>>>>>>> >
>>>>>>>>>> >   - Previous discussion in dev mailing list: [DISCUSS] SPIP:
>>>>>>>>>> > Row-level operations in Data Source V2
>>>>>>>>>> >   <
>>>>>>>>>> https://lists.apache.org/thread/kd8qohrk5h3qx8d6y4lhrm67vnn8p6bv>
>>>>>>>>>> >
>>>>>>>>>> >   - JIRA: SPARK-35801 <
>>>>>>>>>> https://issues.apache.org/jira/browse/SPARK-35801>
>>>>>>>>>> >   - PR for handling DELETE statements:
>>>>>>>>>> > <https://github.com/apache/spark/pull/33008>
>>>>>>>>>> >
>>>>>>>>>> >   - Design doc
>>>>>>>>>> > <
>>>>>>>>>> https://docs.google.com/document/d/12Ywmc47j3l2WF4anG5vL4qlrhT2OKigb7_EbIKhxg60/
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> > Please vote on the SPIP for the next 72 hours:
>>>>>>>>>> >
>>>>>>>>>> > [ ] +1: Accept the proposal as an official SPIP
>>>>>>>>>> > [ ] +0
>>>>>>>>>> > [ ] -1: I don’t think this is a good idea because …
>>>>>>>>>> >
>>>>>>>>>> >
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> > To unsubscribe e-mail: [email protected]
>>>>>>>>>> >
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ---------------------------------------------------------------------
>>>>>>>>>> To unsubscribe e-mail: [email protected]
>>>>>>>>>>
>>>>>>>>>>
>>>>>
>>>>> --
>>>>> Ryan Blue
>>>>> Tabular
>>>>>
>>>> --
>>> John Zhuge
>>>
>>

Reply via email to