[
https://issues.apache.org/jira/browse/IGNITE-21476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-21476:
----------------------------------------
Fix Version/s: 3.2
(was: 3.1)
> Update indexes at the operation timestamp of read-write transaction
> -------------------------------------------------------------------
>
> Key: IGNITE-21476
> URL: https://issues.apache.org/jira/browse/IGNITE-21476
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> To simplify, in IGNITE-20125 we write to all indexes that exist at the
> beginning timestamp of the read-write transaction, but this is not optimal
> and we must write to the indexes available at the operation timestamp.
> But it is also important for us not to forget about the indexes that were
> available at the time the transaction began and disappeared at the time the
> operation was performed; we must also write to them.
> *org.apache.ignite.internal.index.IndexChooser* can help us for this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
