Denis Smirnov authored 11 months ago and Yaroslav Dynnikov committed 11 months ago

Support join chains and fix few parsing bugs.

(cherry picked from commit 33a6928b)

Here's the order of plan stages for memories:

```
$ grep "return Ok" src/governor/plan.rs
return Ok(ConfChange { conf_change }.into());
return Ok(TransferLeadership { to: new_leader }.into());
return Ok(Downgrade { req }.into());
return Ok(CreateReplicaset { master_id, replicaset_id, rpc, op }.into());
return Ok(UpdateTargetReplicasetMaster { op }.into());
return Ok(Replication { targets, master_id, replicaset_peers, req }.into());
return Ok(UpdateCurrentReplicasetMaster { old_master_id, demote, new_master_id, sync_and_promote, replicaset_id, op }.into());
return Ok(ProposeReplicasetStateChanges { op }.into());
return Ok(UpdateTargetVshardConfig { dml }.into());
return Ok(UpdateCurrentVshardConfig { targets, rpc, dml }.into());
return Ok(ShardingBoot { target, rpc, op }.into());
return Ok(ToOnline { target, rpc, req }.into());
return Ok(ApplySchemaChange { rpc, targets }.into());
```

Arseniy Volynets authored 1 year ago and Georgy Moshkin committed 1 year ago

- Add new DML op: Batch, which allows
using multiple dml operations in one
CAS request
- If request has too many dml operations,
the batch will be splitted into multiple
batches, so that each batch can be stored
in raft log

Georgy Moshkin authored 1 year ago and Yaroslav Dynnikov committed 1 year ago

There was a huge amount of boilerplate code with redundant abstractions.
The test code must be as simple as possible and making abstractions over
simple data is not a way to go, especially when builtin types such as
dict do the trick just as easily.

The prettiness of the test code should be out lowest priority.

- add integration tests for pg-like
parameters.

Example usage:

pico.sql([[select $2, $1 from t]], {1, 2})