[
https://issues.apache.org/jira/browse/IGNITE-14198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17287042#comment-17287042
]
Andrey N. Gura commented on IGNITE-14198:
-----------------------------------------
[~ascherbakov] Work is still in progress. But thanks for you comments.
1. It could be usefull in case when you want to subscribe to metastorage
updates from or till particular revision (see watch() which get revision as
parameter). But it's arguable. So consider this method as candidate for removal.
2. Agree.
3. I'm thinking about it, but metastorage in Ignite 2.x doesn't provide batch
methods. May be such methods are not needed. But, agree, batch methods could be
useful.
4. Definitely agree. Work is still in progress.
5. CAS could be easily executed by single conditional update.
6. It is open question at this moment.
7. Arguable, because common classes are shared between client and server. But
work is still in progress.
> Define interface for meta storage client
> ----------------------------------------
>
> Key: IGNITE-14198
> URL: https://issues.apache.org/jira/browse/IGNITE-14198
> Project: Ignite
> Issue Type: New Feature
> Reporter: Andrey N. Gura
> Assignee: Andrey N. Gura
> Priority: Major
> Labels: iep-61, ignite-3
> Fix For: 3.0.0-alpha2
>
>
> Interface for meta storage client should be defined in order to unblock
> development and unit-testing.
> Interface implementation is not needed on this stage.
> We need to crystallize the metastorage interface prototype from the IEP to
> understand how it will be integrated with other system components.
> Need to cover:
> * Asynchrony aspects
> * Possible error codes (connection failure -> unknown result vs Raft failure
> -> known result, etc)
> * Complex multi-updates (aka transactions)
> * Watchers. Each node can watch all updates and filter locally or adjust the
> watched ranges dynamically (consistency is important here)
> These interfaces are considered "client" interfaces as they will be available
> on all nodes in the cluster
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
