ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6624) SQL: IndexingQueryCacheFilter should use immediate partition data if possible
Date Wed, 01 Nov 2017 13:50:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-6624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16234086#comment-16234086
] 

ASF GitHub Bot commented on IGNITE-6624:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/ignite/pull/2847


> SQL: IndexingQueryCacheFilter should use immediate partition data if possible
> -----------------------------------------------------------------------------
>
>                 Key: IGNITE-6624
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6624
>             Project: Ignite
>          Issue Type: Task
>          Components: cache, sql
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Major
>              Labels: performance
>             Fix For: 2.4
>
>
> We need to filter backup keys during query execution. Currently to achieve this we do
the following:
> 1) Get row link
> 2) Materialize the row (!!!)
> 3) Create H2 row (H2 wrapping)
> 4) Then get key from H2 row (unwrapping)
> 5) Calculate partition through affinity function
> What it might look like:
> 1) Get row link
> 2) Get partition from link
> This ticket is to implement working with partitions rather than keys when possible,



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message