You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2021/09/08 18:49:00 UTC
[jira] [Commented] (IGNITE-15382) Decouple API and implementation
for Tuple and Schema.
[ https://issues.apache.org/jira/browse/IGNITE-15382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412135#comment-17412135 ]
Yury Gerzhedovich commented on IGNITE-15382:
--------------------------------------------
[~agura] could you please review the patch
> Decouple API and implementation for Tuple and Schema.
> -----------------------------------------------------
>
> Key: IGNITE-15382
> URL: https://issues.apache.org/jira/browse/IGNITE-15382
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Mashenkov
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: UX, ignite-3
> Fix For: 3.0.0-alpha3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> For now, TupleImpl is a part of public API, but should be internal class.
> SchemaBuilders, on the opposite, relates to a public API, but is hidden in schema-module.
> With Jigsaw it is impossible to have packages of the same name in different modules.
> Let's
> # Move TupleImpl to an internal package of the ignite-table module.
> # Move SchemaBuilders to the public package of the ignite-api module.
> # Use a ServiceLoader for factories for these classes in ignite-api module
--
This message was sent by Atlassian Jira
(v8.3.4#803005)