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

Follow-up for 2b1bd622

> submodule.<name>.branch
>
> A remote branch name for tracking updates in the upstream submodule.
> If the option is not specified, it defaults to the remote HEAD.

The `origin/HEAD` is the default branch in GitLab. In case of
tarantool-sys nowadays it corresponds to `2.11.0-picodata`.

This option is responsible for the correct operation of

    git submodule update --remote tarantool-sys

This allows to operate submodule with the one-liner:

```
git submodule update --remote tarantool-sys/
```

This patch also updates the submodule in a mentioned way.

Current commit introduces distributed SQL in picodata (we use
'sbroad' library). Now it is possible to execute cluster-wide
SQL with 'pico.sql([[query]], {params})' lua method.

Current limitations:
1. DDL is still not implemented in picodata, so space sharding
   is mocked by '_pico_space' space (we'll remove it later).
2. We still have duplicating symbols of the Tarantool module in
   sbroad and in picodata rlibs.
3. We need to reuse piocdata's sharding functions and handle the
   case when different spaces in the query have different sharding
   functions.

Co-authored-by: Georgy Moshkin <gmoshkin@picodata.io>

+ tarantool-sys submodule
+ tarantool-patches directory
+ build.rs build script to patch and build tarantool
+ static linking with tarantool
+ refactoring for cli arguments