<
> yangz...@gmail.com>;
> 发送时间: 2021年1月20日(星期三) 下午3:14
> 收件人: "dev"
> 主题: Doris UNIQUE table supports UPDATE syntax
>
>
>
> ## Background
>
> The current Doris table does not support the update operation, but there
> ar
"dev"
> <
> yangz...@gmail.com>;
> 发送时间: 2021年1月20日(星期三) 下午3:14
> 收件人: "dev"
> 主题: Doris UNIQUE table supports UPDATE syntax
>
>
>
> ## Background
>
> The current Doris tabl
I think the desgin ideas is weird;
Why update statement should be converted into a query and insert statement?
As far as I know, Kudu support update api.
Why not research Kudu's design first?
I prefer to design from the perspective of the storage engine
-- -
Very good proposal.
However I don't see how the isolation is guaranteed between concurrent
transactions in this proposal.
Let's say there is one row in the table
k1 = 1, v1 = 1
There are two concurrent SQL executions, both of which execute the
following statement
"update my_table set v1 = v1 + 1
Hi Zhengguo,
This is a very valuable feature.
Before Doris supports syntax of update, although Doris can also update data
indirectly through the uniq model, it is very cumbersome to use.
The user is required to retain the full amount of new data.
If necessary, I have a better understanding of th
## Background
The current Doris table does not support the update operation, but there
are many scenarios where the data needs to be updated. Due to the batch
delete function we implemented before, it paved the way for the update.
## Syntax
We only support single table update
```
UPDATE table_n
