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

Evgeny Stanilovsky reassigned IGNITE-21281:
-------------------------------------------

    Assignee: Evgeny Stanilovsky

> Sql. Partition pruning. Integrate static partition pruning into MODIFY 
> statements execution pipeline.
> -----------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-21281
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21281
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>    Affects Versions: 3.0.0-beta2
>            Reporter: Maksim Zhuravkov
>            Assignee: Evgeny Stanilovsky
>            Priority: Major
>              Labels: ignite-3
>
> Update PartitionExtractor introduced in 
> https://issues.apache.org/jira/browse/IGNITE-21277 to compile pruning 
> metadata for DML operations.
> In order to that we need to extract values of colocation key columns from 
> input operators to ModifyNodes:
> - For operations that do accept scan operation (e.g. plain INSERT), such 
> information is included in Values and Projection operators (to get values for 
> DEFAULT expression).
> - For that accept scan operation, we should use pruning metadata provided by 
> a scan operator.
> *Some examples*
> Plain insert:
> {code:java}
> INSERT INTO t (colo_col1, colo_col2) VALUES (1, 2), (3, 4)
> Partition pruning metadata: t = [ (col_c1 = 1, col_c2 = 2) ||  (col_c1 = 3, 
> col_c2 = 4)]
> {code}
> Plain update
> {code:java}
> UPDATE t SET col = 100 WHERE pk = 42
> Partition pruning metadata: t = [ (pk = 42) ] // Uses metadata provided by a 
> scan operation
> {code}
> Delete
> {code:java}
> DELETE FROM t WHERE pk = 42
> Partition pruning metadata: t = [ (pk = 42) ] // Uses metadata provided by a 
> scan operation
> {code}
> After this issue is resolved, partition pruning should work for INSERT, 
> UPDATE, MERGE, and DELETE statements.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to