[2pt] feedback: space_object:on_replace()
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
Description
Product: Tarantool
Root document: https://www.tarantool.io/en/doc/latest/reference/reference_lua/box_space/on_replace/
SME: @ alyapunov
Details
<…>gger-functions for on_replace and
before_replacetransactions,
|yield-operations| (explicit or not),
actions that are not allowed to be used in t<…>
https://www.tarantool.io/en/doc/latest/reference/reference_lua/box_space/on_replace/
Even when mvcc is enabled?
ToDo:
- clarify the point with @ alyapunov and add the info
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the root document for box_space:on_replace() and review the sections on transactions, yield operations, and actions that are not allowed in triggers. Clarify with @alyapunov whether these restrictions apply when MVCC is enabled, then update the linked documentation. Done means the MVCC behavior is explicitly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100