[
https://issues.apache.org/jira/browse/IGNITE-14236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17313741#comment-17313741
]
Andrey Mashenkov commented on IGNITE-14236:
-------------------------------------------
[~slava.koptilin], would you please clarify the motivation.
We already have a task [1] done for table public API, where we are not limited
with just key-value case.
In next [2] task I try to elaborate criteria for internal table API and think
we will operate with binary row representation instead of key-value pairs.
Why you use the term "cache" here?
Do you mean a public Cache API over Tables, or some 3-rd party storage? or
internal API for tables?
[1] https://issues.apache.org/jira/browse/IGNITE-14035
[2] https://issues.apache.org/jira/browse/IGNITE-14330
> Provide a new version of cache API
> ----------------------------------
>
> Key: IGNITE-14236
> URL: https://issues.apache.org/jira/browse/IGNITE-14236
> Project: Ignite
> Issue Type: Sub-task
> Reporter: Vyacheslav Koptilin
> Priority: Major
> Labels: ignite-3
>
> Need to provide a minimal cache API that includes at least the following
> methods:
> - reading a value for a given key
> - writing a new value for a given key
> - remove a value for a given key
> - method that determines if the cache contains an entry for the specified
> key.
> - a way to iterate all key/value pairs
> - cache/table size (this method is questionable)
> Additionally, it can be considered adding a way to execute the user's code
> for the specified key - something like {{Cache#invoke()}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
