CAS predicates should always contain the current raft term, because this
is what's explicitly checked in proc_cas.

Note that this will sometimes result in a EntryTermMismatch error
because the latest applied entry may have a different term in case the
election has started but not finished yet.

We could add this check to all the client cas precondition checks, but
it's not a big deal, because we handle the situation correctly anyways.

Rolled back as in raft log roll back, which can happen when a leader
changes to one who doesn't have the entry we persisted.
Not to be confused with DdlAbort.

Nobody cares about the lsn

I'm not sure but I think it was added before we switched to counting
vshard config versions. Basically it was fixing the same A-B-A problem
but only in a single case.

Just goes to show how you shouldn't apply hacky fixes to problems you
don't fully understand.

BTW nobody is ever reading this message, the commit only removes the
code so nobody will ever bump into it going over git blame...

Not used yet

It's called proc_update_instance, not proc_replace_instance, duh!

Previously macros won't work when using solely picoplugin as SDK.
It is fixed in linked tarantool-module MR, this MR introduces tests for that.

Linked [MR](https://git.picodata.io/picodata/picodata/tarantool-module/-/merge_requests/542) in tarantool-module.

feat: support ALTER SYSTEM. It allows to change whitelisted properties from _pico_property table. Currently, changes affect all tiers. Specifying tier will result in an error.

Co-Authored-by: Dmitry Rodionov <d.rodionov@picodata.io>

Co-Authored-by: Emir Vildanov <e.vildanov@picodata.io>

Arseniy Volynets authored 8 months ago and Arseniy Volynets committed 7 months ago

- update sbroad submodule to commit with
new normalization rules
- update integration tests