Dear podling,
This email was sent by an automated system on behalf of the Apache
Incubator PMC. It is an initial reminder to give you plenty of time to
prepare your quarterly board report.
The board meeting is scheduled for Wed, 17 February 2021.
The report for your podling will form a part of th
Hi Wangbo,
In terms of design, I think it is not syntactically rewritten as select +
insert, but should use the query engine to plan read and write operators
(the current operators can be reused) to meet the update requirements.
In addition, Doris itself supports updates from the storage engine.
+1 This is a valuable and most required feature. It makes Doris a fully
qualified SQL supported data warehouse DB.
On Wed, Jan 20, 2021 at 1:57 AM 王博 <506340...@qq.com> wrote:
> I think the desgin ideas is weird;
> Why update statement should be converted into a query and insert statement?
> As f
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
