[jira] [Updated] (IGNITE-15556) Drop SchemaBuilder public API.
[ https://issues.apache.org/jira/browse/IGNITE-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15556: -- Issue Type: Task (was: Improvement) > Drop SchemaBuilder public API. > -- > > Key: IGNITE-15556 > URL: https://issues.apache.org/jira/browse/IGNITE-15556 > Project: Ignite > Issue Type: Task >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: UX, ignite-3 > > Drop SchemaBuilders public API as schema manupulation will be available only > via SQL -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-15556) Drop SchemaBuilder public API.
[ https://issues.apache.org/jira/browse/IGNITE-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15556: -- Description: Drop SchemaBuilders public API as schema manupulation will be available only via SQL (was: SchemaBuilders implements a public API interface and resides in the ignite-schema module. Public API implementation must be hidden from a user to avoid direct usage/instantiation, but we need a factory. This can be achieved in next ways 1. Use ServiceLoader for schema builders factory. This introduces implicit module dependency and a new factory interface/class. 2. Drop interfaces and make schema builders top-level public classes. As there is no need to have interfaces, for now, let's make the schema builder classes public.) > Drop SchemaBuilder public API. > -- > > Key: IGNITE-15556 > URL: https://issues.apache.org/jira/browse/IGNITE-15556 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: UX, ignite-3 > > Drop SchemaBuilders public API as schema manupulation will be available only > via SQL -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-15556) Drop SchemaBuilder public API.
[ https://issues.apache.org/jira/browse/IGNITE-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15556: -- Labels: UX ignite-3 tech-debt (was: UX ignite-3) > Drop SchemaBuilder public API. > -- > > Key: IGNITE-15556 > URL: https://issues.apache.org/jira/browse/IGNITE-15556 > Project: Ignite > Issue Type: Task >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: UX, ignite-3, tech-debt > > Drop SchemaBuilders public API as schema manupulation will be available only > via SQL -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-15556) Drop SchemaBuilder public API.
[ https://issues.apache.org/jira/browse/IGNITE-15556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrey Mashenkov updated IGNITE-15556: -- Summary: Drop SchemaBuilder public API. (was: Replace SchemaBuilder interfaces with class public classes.) > Drop SchemaBuilder public API. > -- > > Key: IGNITE-15556 > URL: https://issues.apache.org/jira/browse/IGNITE-15556 > Project: Ignite > Issue Type: Improvement >Reporter: Andrey Mashenkov >Assignee: Andrey Mashenkov >Priority: Major > Labels: UX, ignite-3 > > SchemaBuilders implements a public API interface and resides in the > ignite-schema module. > Public API implementation must be hidden from a user to avoid direct > usage/instantiation, but we need a factory. > This can be achieved in next ways > 1. Use ServiceLoader for schema builders factory. > This introduces implicit module dependency and a new factory interface/class. > 2. Drop interfaces and make schema builders top-level public classes. > As there is no need to have interfaces, for now, let's make the schema > builder classes public. -- This message was sent by Atlassian Jira (v8.20.7#820007)
