You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2022/04/11 11:23:00 UTC

[jira] [Commented] (IGNITE-16792) Configuration for Default Storage Engine

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

Ivan Bessonov commented on IGNITE-16792:
----------------------------------------

[~ktkalenko@gridgain.com] looks good to me, I'll merge it to main. Thank you!

> Configuration for Default Storage Engine
> ----------------------------------------
>
>                 Key: IGNITE-16792
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16792
>             Project: Ignite
>          Issue Type: Task
>          Components: persistence
>            Reporter: Sergey Chugunov
>            Assignee: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha5
>
>          Time Spent: 3.5h
>  Remaining Estimate: 0h
>
> Pluggable storage concept enables user to set up different storage engines (SE) on the same node e.g. for performance reasons, each table can be hosted only by one storage.
> From DDL point of view SE is specified as part of CREATE TABLE command. But in case of only one SE and some other cases specifying it for each table creates a lot of unnecessary boilerplate code.
> To address this and free user from writing exactly the same code a cluster-wide setting *defaultStorageEngine* should be introduced.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)