You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2019/02/05 12:29:00 UTC

[jira] [Assigned] (IGNITE-11203) SQL: global refactoring

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

Vladimir Ozerov reassigned IGNITE-11203:
----------------------------------------

    Assignee:     (was: Vladimir Ozerov)

> SQL: global refactoring
> -----------------------
>
>                 Key: IGNITE-11203
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11203
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Vladimir Ozerov
>            Priority: Major
>
> Over the years of SQL existence it's logic became overly complex as we never invested enough time into technical debt. Most prominent features that led to over-complication are:
> # Distributed joins
> # Subqueries in spliiter
> # MVCC 
> # Query cancel feature
> # DML
> As a result currently it is too difficult to add new features to the product: we have to spend a lot time figuring what if going on, and loose a lot on introduced bugs.
> General idea of this initiative is to streamline query execution engine as much as possible. The most important things to consider:
> # Simplify H2 connection management: simple pooling, avoid exposing connection when possible
> # Execute MAP and LOCAL queries through the same flow
> # Avoid zig-zag code flow in DML stuff
> # Rework overly complex "query cancel" feature
> # Try to merge partition pruning and distributed join cost calculation



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