[
https://issues.apache.org/jira/browse/IGNITE-21802?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Roman Puchkovskiy updated IGNITE-21802:
---------------------------------------
Description:
Rows are stored in the version (here, I refer to the table version) in which
they were written to the storage. When they are read, they need to be returned
in the table version corresponding to the reading transaction. As such, they
need to be *upgraded* upon read.
We have a bunch of APIs (KV/record views, SQL, JDBC) through which rows can be
read. For each such method, we need to have a test that makes sure that upgrade
happens.
Also, row upgrade might influence write operations (like exact removal and
exact replace in KV APIs). For them, tests are also needed (see IGNITE-21296).
was:
Rows are stored in the version (here, I refer to the table version) in which
they were written to the storage. When they are read, they need to be returned
in the table version corresponding to the reading transaction. As such, they
need to be *upgraded* upon read.
We have a bunch of APIs (KV/record views, SQL, JDBC) through which rows can be
read. For each such method, we need to have a test that makes sure that upgrade
happens.
Also, row upgrade might influence write operations (like exact removal and
exact replace in KV APIs). For them, tests are also needed.
> Add integration tests for row upgrading for all related APIs
> ------------------------------------------------------------
>
> Key: IGNITE-21802
> URL: https://issues.apache.org/jira/browse/IGNITE-21802
> Project: Ignite
> Issue Type: Improvement
> Reporter: Roman Puchkovskiy
> Priority: Major
> Labels: ignite-3
>
> Rows are stored in the version (here, I refer to the table version) in which
> they were written to the storage. When they are read, they need to be
> returned in the table version corresponding to the reading transaction. As
> such, they need to be *upgraded* upon read.
> We have a bunch of APIs (KV/record views, SQL, JDBC) through which rows can
> be read. For each such method, we need to have a test that makes sure that
> upgrade happens.
> Also, row upgrade might influence write operations (like exact removal and
> exact replace in KV APIs). For them, tests are also needed (see IGNITE-21296).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
