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

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

GitHub user tledkov-gridgain opened a pull request:

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

    IGNITE-4650: Scan and SPI queries must go through dedicated query pool

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-4650

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1534.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 #1534
    
----
commit 43ca4e942a3ad1f88cbc0919e2ec60c18e4765dd
Author: tledkov-gridgain <[email protected]>
Date:   2017-02-14T13:38:22Z

    IGNITE-4650: all queries go through QUERY_POOL

commit dac00b1e092b1cc391e18b3517de4a2347b0944a
Author: tledkov-gridgain <[email protected]>
Date:   2017-02-14T14:55:09Z

    Merge branch 'ignite-2.0' into ignite-4650

commit 11e5e611f307b596771dd644fb399e9903b33ffd
Author: tledkov-gridgain <[email protected]>
Date:   2017-02-15T07:45:22Z

    IGNITE-4650: use QUERY_POOL for local queries

----


> Scan and SPI queries must go through dedicated query pool
> ---------------------------------------------------------
>
>                 Key: IGNITE-4650
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4650
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>            Reporter: Vladimir Ozerov
>            Assignee: Taras Ledkov
>             Fix For: 2.0
>
>
> In IGNITE-4105 we introduced separate thread pool for queries. Currently it 
> is used only for {{SQL}} queries. 
> Need to make sure that it is also used for {{SCAN}} and {{SPI}} queries.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to