This commit embeds in plugins a new variable, containing picoplugin
version used to build it. If this version differs from the picodata version
when the plugin gets loaded, the loading fails with an error reporting
the expected and the current versions. This check can be disabled via env
PICODATA_UNSAFE_DISABLE_PLUGIN_COMPATIBILITY_CHECK.

Anatoly Popov authored 1 year ago and Yaroslav Dynnikov committed 1 year ago

1. http-server:

    1. Get info about tiers from _pico_tier
    2. Get info about instance addresses from:
        - http: lua api
        - binary:  _pico_peer_addresses
    3. Switch from arrays to map where it makes sense
    4. Compose all the data to `cluster_state` object
    5. Get version information for lua api.

2. Tests:

    1. Add DeepDiff package to better diff for json
    2. Amend tests to new specification
    3. Get picodata version via lua api and use it in asserts

3. Chore:

    1. Add .envrc and .direnv to .gitingore (direnv specific files)
    2. Add .vscode to .gitignore.

Signed-off-by: Anatoly Popov <a.popov@picodata.io>

To run the test you need xk6 installed
(https://github.com/tarantool/xk6-tarantool).

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>

The traits to plug new engines became more clear. It would help us
while implementing the picodata engine.

We want to get reproducible builds. Cargo.lock does exactly this.
On the start of the development we were following the rule that
"libraries does not include cargo.lock in git, binary does".
However we misinterpreted the role of Sbroad. It is built as a "cdylib"
so we should treat it as an executable and include cargo.lock

Close https://gitlab.com/picodata/picodata/picodata/-/issues/23