[
https://issues.apache.org/jira/browse/IGNITE-20125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17793205#comment-17793205
]
Roman Puchkovskiy commented on IGNITE-20125:
--------------------------------------------
The patch looks good to me
> Write to write-compatible indices when writing to partition
> -----------------------------------------------------------
>
> Key: IGNITE-20125
> URL: https://issues.apache.org/jira/browse/IGNITE-20125
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Assignee: Kirill Tkalenko
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> For each operation that is writing, the operation’s timestamp (which moves
> partition’s SafeTime forward) T~op~ is used to get the schema corresponding
> to the operation. When it’s obtained, all writable (STARTING, READY,
> STOPPING) indices that are write-compatible at T~op~ are taken, and the
> current operation writes to them all.
> An index is write-compatible at timestamp T~op~ if for each column of the
> index the following holds: the column was not dropped at all, or it was
> dropped strictly after T~op~.
> If an index does not exist anymore at T~op~, the write to it is just ignored,
> the transaction is not aborted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
