[
https://issues.apache.org/jira/browse/IGNITE-21054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-21054:
---------------------------------------
Description:
For each read/write operation in an RW transaction, we check that the schema of
the table has not changed (to implement fail-fast behavior).
When doing so, we do 'schema sync' (implying a possible wait) at
operationTimestamp. It seems that the 'schema sync' is not necessary (it's not
a problem if we check against a slightly outdated schema [as it cannot be too
outdated, it is not older than the schema on which the transaction had
started]).
This must be considered carefully first (maybe there is some reason to keep the
checks). We should do it after we design the index build procedure (as it
requires to take current schema for each write operation).
> Do not do schema sync await on every read/write operation in RW transaction
> ---------------------------------------------------------------------------
>
> Key: IGNITE-21054
> URL: https://issues.apache.org/jira/browse/IGNITE-21054
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
>
> For each read/write operation in an RW transaction, we check that the schema
> of the table has not changed (to implement fail-fast behavior).
> When doing so, we do 'schema sync' (implying a possible wait) at
> operationTimestamp. It seems that the 'schema sync' is not necessary (it's
> not a problem if we check against a slightly outdated schema [as it cannot be
> too outdated, it is not older than the schema on which the transaction had
> started]).
> This must be considered carefully first (maybe there is some reason to keep
> the checks). We should do it after we design the index build procedure (as it
> requires to take current schema for each write operation).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
