[
https://issues.apache.org/jira/browse/IGNITE-9630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16711126#comment-16711126
]
Vladimir Ozerov commented on IGNITE-9630:
-----------------------------------------
[~jooger], addressing your comments:
1) {{IgniteH2Indexing.wrap}} method is context-bound, so it is not static stuff
2) Cursor refactoring is out of scope of this ticket
3) {{PartitionExtractor}} return null in case we cannot determine partitions
for at least one map query. That is, if at least one query require broadcast,
then all other queries will be broadcasted as well. This is the same behavior
as in old partition extraction logic. This is a kind of architectural flaw of
current partition processing logic - set of partitions are defined on query
message level (see GridH2QueryRequest.qryParts). Once we get rid of this
limitation, we will be able to send every map query directly to it's relevant
partitions. But this is out of scope of this ticket.
> 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)
