You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2018/07/23 22:38:00 UTC

[jira] [Commented] (IGNITE-8977) Need to update distributed SQL page

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

Denis Magda commented on IGNITE-8977:
-------------------------------------

[~dsetrakyan], please review:
https://ignite.apache.org/features/sql.html

> Need to update distributed SQL page
> -----------------------------------
>
>                 Key: IGNITE-8977
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8977
>             Project: Ignite
>          Issue Type: Improvement
>          Components: documentation
>            Reporter: Dmitriy Setrakyan
>            Assignee: Prachi Garg
>            Priority: Blocker
>             Fix For: 2.7
>
>
> Main goal - less text, better structure.
> Let's add the following sections:
>  # Distributed SQL Indexes
>  # {color:#333333}Distributed SQL JOINs{color}
>  # {color:#333333}Memory-only{color}
>  # {color:#333333}Native Persistence{color}
>  # {color:#333333}Memory Management - here we should mention that due to Ignite memory management policies, the most used indexes will always end up being cached in memory, even when the persistence is enabled.{color}
>  # {color:#333333}3rd Party Databases - here we should mention that Ignite SQL does write-through to 3rd party databases, if needed.{color}
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)