[
https://issues.apache.org/jira/browse/IGNITE-17078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-17078:
---------------------------------------
Description:
Today, we have two approaches to use Versioned value object:
1) Used it for modifying some preparing value until revision will be completed.
For the porpoise, we use constructor like this:
{code:java}
VersionedValue<Integer> vv = new VersionedValue<>(REGISTER);
{code}
2) Complete the value manually for each revision. There is no possible notify.
In this case, we are force to use a constructor with {{null}} argument:
{code:java}
VersionedValue<Integer> vv = new VersionedValue<>(null);
{code}
I propose to extend Value object functionality in order to completion will be
able to happen due to explicit {{complete()}} invocation or due to the revision
notification, if the token in not closed before.
> Support as a storage revision notification well as a manual completion
> simultaneously for Versioned value object
> ----------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-17078
> URL: https://issues.apache.org/jira/browse/IGNITE-17078
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
>
> Today, we have two approaches to use Versioned value object:
> 1) Used it for modifying some preparing value until revision will be
> completed.
> For the porpoise, we use constructor like this:
> {code:java}
> VersionedValue<Integer> vv = new VersionedValue<>(REGISTER);
> {code}
> 2) Complete the value manually for each revision. There is no possible notify.
> In this case, we are force to use a constructor with {{null}} argument:
> {code:java}
> VersionedValue<Integer> vv = new VersionedValue<>(null);
> {code}
> I propose to extend Value object functionality in order to completion will be
> able to happen due to explicit {{complete()}} invocation or due to the
> revision notification, if the token in not closed before.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
