You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (Jira)" <ji...@apache.org> on 2021/03/17 09:51:00 UTC

[jira] [Commented] (IGNITE-13748) Schema configuration public API

    [ https://issues.apache.org/jira/browse/IGNITE-13748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17303246#comment-17303246 ] 

Alexey Goncharuk commented on IGNITE-13748:
-------------------------------------------

Looks good from my side. I think we can merge and start collecting feedback from the community.

> Schema configuration public API
> -------------------------------
>
>                 Key: IGNITE-13748
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13748
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Andrey Mashenkov
>            Assignee: Andrey Mashenkov
>            Priority: Major
>              Labels: iep-54, ignite-3
>             Fix For: 3.0.0-alpha2
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Let's implement a public API classes for initial schema declaration. Considering next:
>  * It should be possible to create schema without having any Class instance, like we do now with QueryEntity. 
>  * -Automatic schema creation based on annotated classes, like we have in ccfg.setIndexedTypes()- IGNITE-13749
>  * -Transient fields semantic.- IGNITE-13749
>  * Using builder pattern for schema configuration.
>  * Split type-system into internal native-types (introduced IGNITE-13617) and public API types. The latest ones should be portable (e.g. could be used in .Net)
>  * API can be extracted to separate module that will not have any dependency on other Ignite modules.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)