[ 
https://issues.apache.org/jira/browse/IGNITE-25721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn updated IGNITE-25721:
------------------------------------
    Description: 
See discussion in the PR for IGNITE-24659:

https://github.com/apache/ignite-3/pull/6059#discussion_r2158131937

{code}
Do I understand correctly it's not needed when an object constructed on a job 
initiator side because we don't need to propagate OTS from a client to a server 
?
Let's at least add a javadoc comment explaining nullable condition.
{code}

  was:
See discussion in the PR for IGNITE-24659:

https://github.com/apache/ignite-3/pull/6059#discussion_r2158131937


> Clarify ComputeJobDataHolder.observableTimestamp nullability
> ------------------------------------------------------------
>
>                 Key: IGNITE-25721
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25721
>             Project: Ignite
>          Issue Type: Improvement
>          Components: compute ai3
>            Reporter: Pavel Tupitsyn
>            Assignee: Pavel Tupitsyn
>            Priority: Minor
>              Labels: ignite-3
>
> See discussion in the PR for IGNITE-24659:
> https://github.com/apache/ignite-3/pull/6059#discussion_r2158131937
> {code}
> Do I understand correctly it's not needed when an object constructed on a job 
> initiator side because we don't need to propagate OTS from a client to a 
> server ?
> Let's at least add a javadoc comment explaining nullable condition.
> {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to