You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (Jira)" <ji...@apache.org> on 2022/08/26 15:20:00 UTC
[jira] [Updated] (IGNITE-17583) Extract BinaryTuple into a separate module to reuse on client
[ https://issues.apache.org/jira/browse/IGNITE-17583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-17583:
------------------------------------
Summary: Extract BinaryTuple into a separate module to reuse on client (was: Extract BinaryTuple into a separate module to reuse on lient)
> Extract BinaryTuple into a separate module to reuse on client
> -------------------------------------------------------------
>
> Key: IGNITE-17583
> URL: https://issues.apache.org/jira/browse/IGNITE-17583
> Project: Ignite
> Issue Type: Task
> Components: thin client
> Affects Versions: 3.0.0-alpha5
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: iep-92, ignite-3
> Fix For: 3.0.0-alpha6
>
>
> *BinaryTuple* related types are currently located in *ignite-schema* module and coupled to internal schema-related types like *NativeTypeSpec*.
> However, those schema-related things are not required for building and parsing binary tuples.
> * Decouple the logic from internal schema types.
> * Move to a separate module that can be referenced from client module.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)