Re: upsert base on copy on write mode

Typo: Maybe the discussion is very clear before.-> Maybe the discussion is NOT very clear before. Thanks OpenInx. I was thinking to add an interface DeleteRows and an API to table so that one could do things like: DeleteRows deleteRows = table.newRowLevelDelete(); deleteRows.deleteByFilter(Filter

Re: upsert base on copy on write mode

I think we should abstract the API firstly, then implement the MOR. COW is also a necessary implementation, but it's easy to implement and no so urgent. On Tue, Mar 3, 2020 at 3:45 PM Junjie Chen wrote: > Thanks, Ryan > > Maybe the discussion is very clear before. Actually, we have built an > in

Re: upsert base on copy on write mode

Thanks, Ryan Maybe the discussion is very clear before. Actually, we have built an internal implementation for update and delete via copy on write mode. Some others may also have their internal implementation as well. What I propose is to provide a general framework or APIs set that support both c

Re: upsert base on copy on write mode

It should be possible to build an implementation of MERGE INTO in Spark now, using the validation that Anton added in #351 . I think he can provide some more context. On Wed, Feb 26, 2020 at 7:42 AM Junjie Chen wrote: > Hi devs > > We are wor

upsert base on copy on write mode

Hi devs We are working on row level delete milestone for upsert feature in merge on read mode. In the meantime, I think it may be useful to have a copy on write implementation. For example, we can implement upsert with spark, so that we can finalize the common APIs that upsert may need and also we