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

[jira] [Updated] (IGNITE-12899) Calcite integration. Distribution multitrait

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

Igor Seliverstov updated IGNITE-12899:
--------------------------------------
    Description: 
Currently Ignite nodes have single distribution value which isn't true in several cases like:
 # a partitioned table with a key alias should have 2 distribution traits: by _key and by key alias (id for example) - without distribution by _key column almost impossible to implement IGNITE-12692
 # After inner / cross join the result should have several hash distributions (by left and by right keys) - it may be important on join transpose optimization
 # On project a source distribution key may appear more than once, so the result should contain a distribution for each distribution key position.

  was:
Currently Ignite nodes have single distribution value which isn't true in several cases like:
 # a partitioned table with a key alias should have 2 distribution traits: by _key and by key alias (id for example) - without distribution by _key column almost impossible to implement IGNITE-12692
 # After inner / cross join the result should have several hash distributions (by left and by right keys) - it may be important on join transpose optimization


> Calcite integration. Distribution multitrait
> --------------------------------------------
>
>                 Key: IGNITE-12899
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12899
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Igor Seliverstov
>            Priority: Major
>
> Currently Ignite nodes have single distribution value which isn't true in several cases like:
>  # a partitioned table with a key alias should have 2 distribution traits: by _key and by key alias (id for example) - without distribution by _key column almost impossible to implement IGNITE-12692
>  # After inner / cross join the result should have several hash distributions (by left and by right keys) - it may be important on join transpose optimization
>  # On project a source distribution key may appear more than once, so the result should contain a distribution for each distribution key position.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)