[
https://issues.apache.org/jira/browse/IGNITE-6588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198559#comment-16198559
]
ASF GitHub Bot commented on IGNITE-6588:
----------------------------------------
GitHub user devozerov opened a pull request:
https://github.com/apache/ignite/pull/2825
IGNITE-6588
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-6588
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/2825.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2825
----
commit 1723fbdf3d8ed9c3e81f4388eedc0c64653299c1
Author: devozerov <[email protected]>
Date: 2017-10-10T12:00:01Z
Done.
----
> SQL: optimize segment resolution in GridH2IndexBase when index is not
> segmented
> -------------------------------------------------------------------------------
>
> Key: IGNITE-6588
> URL: https://issues.apache.org/jira/browse/IGNITE-6588
> Project: Ignite
> Issue Type: Task
> Components: sql
> Affects Versions: 2.1
> Reporter: Vladimir Ozerov
> Assignee: Vladimir Ozerov
> Fix For: 2.3
>
>
> Currently we go through relatively slow path to determine index segment -
> unwrap key, resolved partition, etc..
> All of this is not needed when index is not segmented.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
