Support different space engines
At least for sharded spaces it's reasonable to provide a choice - memtx or vinyl.
And global spaces should always stay memtx in my opinion.
See: RFC - System Spaces
At least for sharded spaces it's reasonable to provide a choice - memtx or vinyl.
And global spaces should always stay memtx in my opinion.
See: RFC - System Spaces
changed milestone to %23.12.0
added backlog label
mentioned in issue sbroad#473 (closed)
assigned to @gmoshkin
And global spaces should always stay memtx in my opinion.
@rosik what is the reason for this constraint?
The result of earlier verbal discussion.
At first, there is a tech difficulty. Operating global spaces requires committing some data (at least applied_index
) atomically with changes itself, but we don't have cross-engine transactions.
The second reason is that the demand has no clear user reasoning to me.
mentioned in merge request !641 (merged)
changed the description
assigned to @senya_volynets and unassigned @gmoshkin
closed with merge request !641 (merged)