Close #635

Reasons:
- it's not safe to split raft entries as atomicness is lost
- the original feature was not tested

godzie44 authored 10 months ago and Georgy Moshkin committed 10 months ago

chore(plugins): `update_plugin_tiers` API call is split into `service_append_tier` and `service_remove_tier` calls

godzie44 authored 1 year ago and Yaroslav Dynnikov committed 10 months ago

Plugin topology is a mapping plugin service to tiers.

Introduce new `pico.update_plugin_tiers` API.
This function may be used for control
where plugin services must be running and where not.

Plugin integration tests have also been refactored.

godzie44 authored 1 year ago and Yaroslav Dynnikov committed 11 months ago

Now for installation and enable plugin, there are two steps instead of one
(`pico.load_plugin` previously).
1. Install plugin (`pico.install_plugin`):
validate plugin, create system tables.
2. Enable plugin (`pico.enable_plugin`):
loads plugin into instances memory, call `on_start` callback.

Same for a plugin removing process (`pico.remove_plugin` previously):
1. Disable plugin (`pico.disable_plugin`): call `on_stop` callbacks, drop
plugin from instances.
2. Remove plugin (`pico.remove_plugin`):
remove plugin meta from system tables.

BREAKING CHANGE: "name" index in the _pico_index has changed:
previously it guarantees uniqueness for a pair of (space_id,
index_name). Now index name must be unique among the cluster.
So, all the global indexes for _pico tables were renamed.

BREAKING CHANGE: _pico_index structure has changed.

The reason for refactoring is the request for the cluster wide
indexes with all possible options. The old structure didn't allow
us to support them all.

godzie44 authored 1 year ago and Yaroslav Dynnikov committed 11 months ago

Introduce a plugin system for picodata cluster.
Plugin system contains:
- `picoplugin` crate with plugin interfaces.
This crate exposes plugin interfaces for user implementation and API
that used by picodata to interact with plugin as with a code from dynamic library.
- Support for plugin work cycle in picodata instance work cycle.
Picodata instance interacts with running plugin by `PluginManager`
component.
Typically, plugins react to events that occur in instance or whole cluster.
- New lua API with plugin CRUD actions.
    - pico.create_plugin - load a new plugin into picodata cluster
    - pico.remove_plugin - remove plugin from picodata cluster
    - pico.update_plugin_config - update plugin service configuration

(cherry picked from commit 39f8885b)

(cherry picked from commit 8593bc2f)

Egor Ivkov authored 1 year ago and Yaroslav Dynnikov committed 11 months ago

also removes new_database_created event

(cherry picked from commit b5179bb1)

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

Also here we refactor all the places where we checked command line
parameters, because now PicodataConfig is the main source of this
information.

- add new ddl opcode for renaming procedure
- update sbroad submodule to get sql support
- syntax:

alter procedure "foo" rename to "bar" option(timeout=3)
alter procedure "foo"(int, int) rename to "bar"