[
https://issues.apache.org/jira/browse/IGNITE-25718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evgeny Stanilovsky updated IGNITE-25718:
----------------------------------------
Fix Version/s: 3.2
(was: 3.1)
> Compute job does not observe changes made from client
> -----------------------------------------------------
>
> Key: IGNITE-25718
> URL: https://issues.apache.org/jira/browse/IGNITE-25718
> Project: Ignite
> Issue Type: Bug
> Components: compute ai3, thin clients ai3
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: ignite-3
> Fix For: 3.2
>
>
> See IGNITE-25718 - we need to solve the opposite problem:
> * Client inserts a row R that goes to node A
> * Client invokes compute job that goes to node B, the job does not see the
> row R because it uses older timestamp to read data
> Discuss with [~vpyatkov] and [~ascherbakov] . Naive solution is to bump
> *org.apache.ignite.internal.tx.impl.IgniteTransactionsImpl#observableTimestampTracker*,
> but that might have performance repercussions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
