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/14 15:33:00 UTC
[jira] [Closed] (IGNITE-8598) SQL: ability to control partition
pruning with explicit affinity column definition
[ https://issues.apache.org/jira/browse/IGNITE-8598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Ozerov closed IGNITE-8598.
-----------------------------------
> SQL: ability to control partition pruning with explicit affinity column definition
> ----------------------------------------------------------------------------------
>
> Key: IGNITE-8598
> URL: https://issues.apache.org/jira/browse/IGNITE-8598
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Priority: Major
>
> Affinity functions are applicable to keys only. Sometimes users may have complex affinity calculation logic, so that partition pruning optimization is not applicable. E.g. this custom {{AffinityKeyMapper}}. However, there is a chance that partition could be calculated from some attribute of {{value}}.
> It would be nice to force our engine to treat some attribute as affinity key even though it is not marked as {{AffinityKeyMapped}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)