You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexander Lapin (Jira)" <ji...@apache.org> on 2022/05/30 20:09:00 UTC

[jira] [Updated] (IGNITE-15546) Remove java create/alter/dropTable api from within Ignite public API, use DDL instead

     [ https://issues.apache.org/jira/browse/IGNITE-15546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexander Lapin updated IGNITE-15546:
-------------------------------------
    Summary: Remove java create/alter/dropTable api from within Ignite public API, use DDL instead  (was: Replace Consumer<TableChanger> from Tables methods.)

> Remove java create/alter/dropTable api from within Ignite public API, use DDL instead
> -------------------------------------------------------------------------------------
>
>                 Key: IGNITE-15546
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15546
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey Mashenkov
>            Priority: Major
>              Labels: ignite-3
>
> As of now, Tables methods accept Consumer<TableChanger> as a configuration.
> TableChanger looks weird on "create" methods because a user expects some initial configuration to be passed to "create" methods (at least).
> I propose to replace TableChanger argument with some configuration objects.
> We already have schema builders for schema and just need  few changes for table config.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)