[GitHub] ignite pull request #2193: IGNITE-5468

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[GitHub] ignite pull request #2193: IGNITE-5468

andrey-kuznetsov
GitHub user BiryukovVA opened a pull request:

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

    IGNITE-5468

    IGNITE-5468: Added the ability to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE and IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE via cache configuration

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

    $ git pull https://github.com/BiryukovVA/ignite IGNITE-5468

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

    https://github.com/apache/ignite/pull/2193.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 #2193
   
----
commit eeb9a4cf5d868c7c2361a7b9b83b0245ee5970c3
Author: Vitaliy <[hidden email]>
Date:   2017-06-26T09:37:16Z

    IGNITE-5468: Added the ability to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE and IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE via cache configuration

commit 6446d085419c140f03511e1867c72069d47b3055
Author: Vitaliy <[hidden email]>
Date:   2017-06-26T11:17:10Z

    IGNITE-5468: Refactoring.

commit 08734b11c7456aee6292ecc3b0778a8187fe76a4
Author: Vitaliy <[hidden email]>
Date:   2017-06-26T09:37:16Z

    IGNITE-5468: Added the ability to set IGNITE_SQL_MERGE_TABLE_MAX_SIZE and IGNITE_SQL_MERGE_TABLE_PREFETCH_SIZE via cache configuration

commit 4a2c75c785c6a7403a0e7b9a05a3b3a07b888e5e
Author: Vitaliy <[hidden email]>
Date:   2017-06-26T11:17:10Z

    IGNITE-5468: Refactoring.

commit 2aa81f94b31c94efde0ad7d765bd4a70cb486e32
Author: Vitaliy <[hidden email]>
Date:   2017-06-26T12:52:21Z

    Merge remote-tracking branch 'origin/IGNITE-5468' into IGNITE-5468

----


---
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 [hidden email] or file a JIRA ticket
with INFRA.
---