You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2024/01/25 06:28:00 UTC
[jira] [Assigned] (IGNITE-21310) Sql. Partition pruning. Introduce partition provider
[ https://issues.apache.org/jira/browse/IGNITE-21310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Evgeny Stanilovsky reassigned IGNITE-21310:
-------------------------------------------
Assignee: Evgeny Stanilovsky
> Sql. Partition pruning. Introduce partition provider
> ----------------------------------------------------
>
> Key: IGNITE-21310
> URL: https://issues.apache.org/jira/browse/IGNITE-21310
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Evgeny Stanilovsky
> Priority: Major
> Labels: ignite-3
>
> In order to implement partition pruning, we need a component that will return partition id by given colocation keys' values. We already have HashCalculator+ColocationUtils to calculate colocation hash and TypesAwareHashFunction which does pretty match the same thing but for sql.
> My proposal is to introduce component that will consume values similarly to HashCalculator but will return particular partition id with regard to table's column types and number of its partitions.
> As part of this ticket, let's integrate new component into {{org.apache.ignite.internal.sql.engine.trait.Partitioned}} destination function.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)