Currently only 2 cases are supported:
- config_file
- commandline_or_environment

Before this change we would silently replace an instance with current
grade not Online if a new instance with the same name wanted to join.
This was a mistake as it would allow a race condition when joining
several instances at once.

- update sbroad submodule to commit with support of to_char
- add some integration tests, note: there are also
integration tests in cartridge
- This function is implemented as calling `format` on
given datetime object
- Usage:

to_char(datetime, format)

select to_char(datetime_column, 'Last updated: %Y-%m-%d') from t

Second argument is optional and could be specified as `null`:

select to_char(datetime_column, null) from t

- format is specified with the same rules as in strftime function
https://man.freebsd.org/cgi/man.cgi?query=strftime&sektion=3

Arseniy Volynets authored 11 months ago and Denis Smirnov committed 11 months ago

- update sbroad submodule with support of
datetime type and new `to_date` builtin
function.
- initialize sbroad builtin functions in
init common. Currently there is only one
builtin function `to_date`
- add integration tests for datetime types
- update tarantool module to commit with
fixes for datetime deserialization

We have recently replaced String with SmolStr in sbroad.
As a result, we need to make corresponding changes in
picodata as it uses sbroad-core for cluster SQL.

Add stage to run stress tests in downstream pipeline for each commit

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 11 months 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