Index Structure Transaction Supports

[mapleFU]

Search before asking

• I had searched in the issues and found no similar issues.

Motivation

In databases, transactions is both for external and internal usages. External usages like explicit transactions "BEGIN" "END" with multiple operations. Internal usage is also a large part of transactions, basically, the usage would like:

1. Index creation. The index build might base on a "data snapshot", and after index is first build, the system might catch up incoming logs to build the index
2. Index maintainance. When insertion to data, the correspond index should being updated. This is also a "internal transaction"
3. And internal structure change, syncing might all related to index etc...

Solution

in Kvrocks, we also need Transaction for secondary index:

• IndexUpdater, GlobalIndexer, IndexManager might need gurantee transaction syntax
• Follow or force transaction in Index related module

Are you willing to submit a PR?

• I'm willing to submit a PR!

[mapleFU]

cc @PragmaTwice @PokIsemaine

[PokIsemaine]

I think the engine::Context for each command needs to be promoted to Connection::ExecuteCommand, and ExecuteCommand also accepts an engine::Context parameter. This allows multiple commands (or internal procedures) to use the same engine::Context while facilitating unified management

[PragmaTwice]

Refer to #2563.

Also same for scripting transaction optimization.