ignite-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From tledkov-gridgain <...@git.apache.org>
Subject [GitHub] ignite pull request #1534: IGNITE-4650: Scan and SPI queries must go through...
Date Wed, 15 Feb 2017 07:47:28 GMT
GitHub user tledkov-gridgain opened a pull request:


    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:


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 <tledkov@gridgain.com>
Date:   2017-02-14T13:38:22Z

    IGNITE-4650: all queries go through QUERY_POOL

commit dac00b1e092b1cc391e18b3517de4a2347b0944a
Author: tledkov-gridgain <tledkov@gridgain.com>
Date:   2017-02-14T14:55:09Z

    Merge branch 'ignite-2.0' into ignite-4650

commit 11e5e611f307b596771dd644fb399e9903b33ffd
Author: tledkov-gridgain <tledkov@gridgain.com>
Date:   2017-02-15T07:45:22Z

    IGNITE-4650: use QUERY_POOL for local queries


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.

View raw message