[
https://issues.apache.org/jira/browse/IGNITE-9630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16709829#comment-16709829
]
Vladimir Ozerov edited comment on IGNITE-9630 at 12/5/18 9:30 AM:
------------------------------------------------------------------
Business logic is ready for preliminary review. Tests are not written yet.
Design considerations:
# {{WHERE}} is converted to a tree. Then we attempt to optimize and flatten it.
Finally, arguments are extracted.
# This tree will be passed over a wire to thin clients in future.
# Fixed partition merge logic when there are multiple map queries: we merge
only when both queries extracted partitions from the same table. In future this
merge should be deleted. Instead, every map query should operate on it's own
set of partitions, no need to merge them.
was (Author: vozerov):
Business logic is ready for preliminary review. Tests is yet to be written.
Design considerations:
# {{WHERE}} is converted to a tree. Then we attempt to optimize and flatten it.
Finally, arguments are extracted.
# This tree will be passed over a wire to thin clients in future.
# Fixed partition merge logic when there are multiple map queries: we merge
only when both queries extracted partitions from the same table. In future this
merge should be deleted. Instead, every map query should operate on it's own
set of partitions, no need to merge them.
> Partitions intersection for AND condition of same key
> -----------------------------------------------------
>
> Key: IGNITE-9630
> URL: https://issues.apache.org/jira/browse/IGNITE-9630
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Affects Versions: 2.7
> Reporter: Sergey Grimstad
> Assignee: Vladimir Ozerov
> Priority: Major
> Labels: iep-24
> Fix For: 2.8
>
>
> GridSqlQuerySplitter when extractPartition for AND operation type should
> calculate intersection of resolved partitions for the same key
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
