[
https://issues.apache.org/jira/browse/IGNITE-21383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vladislav Pyatkov updated IGNITE-21383:
---------------------------------------
Description:
h3. Motivation
Currently, the KV API requires a key tuple to get or put a value. There is a
typical pattern:
{code}
kvView.put(null, Tuple.create().set("key", i), Tuple.create().set("valInt", i));
kvView.get(null, Tuple.create().set("key", i));
{code}
Beside that, we spend more time validating field name limitations.
!TupleBuildGraph.png!
h3. Definition of done
We do not parse field names to put or get values from KV views.
Probably we will be able to make a tuple template for the known table schema
and provide access to it through an API.
was:
h3. Motivation
Currently, the KV API requires a key tuple to get or put a value. There is a
typical pattern:
{code}
kvView.put(null, Tuple.create().set("key", i), Tuple.create().set("valInt", i));
kvView.get(null, Tuple.create().set("key", i));
{code}
Beside that, we spend more time validating field name limitations.
h3. Definition of done
We do not parse field names to put or get values from KV views.
Probably we will be able to make a tuple template for the known table schema
and provide access to it through an API.
> Optimize binary tuple creation
> ------------------------------
>
> Key: IGNITE-21383
> URL: https://issues.apache.org/jira/browse/IGNITE-21383
> Project: Ignite
> Issue Type: Improvement
> Reporter: Vladislav Pyatkov
> Priority: Major
> Labels: ignite-3
> Attachments: TupleBuildGraph.png
>
>
> h3. Motivation
> Currently, the KV API requires a key tuple to get or put a value. There is a
> typical pattern:
> {code}
> kvView.put(null, Tuple.create().set("key", i), Tuple.create().set("valInt",
> i));
> kvView.get(null, Tuple.create().set("key", i));
> {code}
> Beside that, we spend more time validating field name limitations.
> !TupleBuildGraph.png!
> h3. Definition of done
> We do not parse field names to put or get values from KV views.
> Probably we will be able to make a tuple template for the known table schema
> and provide access to it through an API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
