feature(plugin migration): use md5 from migration files meta for to confirm consistency of migrations between versions

Closes #652

- add `migration_up` and `migration_down` lua API functions
- now the migration mechanism in plugins takes into account the plugin version and, accordingly, previous applied migrations
- add _pico_plugin_migration system table

Closes #683

Supported in:
picodata admin (lua/sql mode)
picodata connect

Georgy Moshkin authored 9 months ago and Yaroslav Dynnikov committed 9 months ago

This is needed because we don't support converting decimals to float
yet, but our SQL engine inserts decimal values by default.

Georgy Moshkin authored 9 months ago and Yaroslav Dynnikov committed 9 months ago

This fixes the A-B-A problem which was observed in the issue
https://git.picodata.io/picodata/picodata/picodata/-/issues/763.

Closes #763

default tier persisted only in the absence of configuration file

This partially reverts commit 6f0cee63.

godzie44 authored 9 months ago and Dmitry Rodionov committed 9 months ago

feature(plugin): add plugin version rules: only one plugin version may be enabled at the same time on instance

Previously, we retrieved the row count using rows.len(), where rows was an
iterator that returned the remaining number of rows instead of the
total number of rows sent.

Make it possible to pass enabled injections at process startup via env
variables.

If initial call to vshard.router.bootstrap failed with taimeout then
following calls return cluster already bootstrapped error. Make
proc_sharding_bootstrap treat this error as successful bootstrap.

Close: https://git.picodata.io/picodata/picodata/picodata/-/issues/751