You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2021/09/22 09:46:00 UTC
[jira] [Updated] (IGNITE-15341) Table API refactoring.
[ https://issues.apache.org/jira/browse/IGNITE-15341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Mashenkov updated IGNITE-15341:
--------------------------------------
Summary: Table API refactoring. (was: Table API. Rename confusing method getOrCreateTable.)
> Table API refactoring.
> ----------------------
>
> Key: IGNITE-15341
> URL: https://issues.apache.org/jira/browse/IGNITE-15341
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Mashenkov
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: UX, ignite-3
> Fix For: 3.0.0-alpha3
>
>
> `IgniteTables.getOrCreateTable` method accepts table configuration as an argument.
> However, it is not clear if there is a guarantee the returned table will have the configuration equals to the provided one.
>
> Actually, the method creates a table if it does not exist, otherwise returns existed table instance.
> Let's rename it to `createTableIfNotExists` to be consistent with the current behaviour.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)