[GitHub] ignite pull request #4963: IGNITE-9861: Authorization object names must alwa...

2018-10-11 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-9861: Authorization object names must always be non-null.



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

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

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

https://github.com/apache/ignite/pull/4963.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 #4963


commit f97dfaec3baf9d60ae1c0c8683db2e7281533b6a
Author: Vitaliy Biryukov 
Date:   2018-10-11T18:43:53Z

IGNITE-9861: Authorization object names must always be non-null.




---


[GitHub] ignite pull request #4552: IGNITE-9267: Deadlock between unsuccessful client...

2018-08-15 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-9267: Deadlock between unsuccessful client reconnecting and stopping.



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

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

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

https://github.com/apache/ignite/pull/4552.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 #4552


commit 15bbbc743628da356927f863f6e24d48b9a49d92
Author: Vitaliy Biryukov 
Date:   2018-08-15T19:48:41Z

IGNITE-9267: Deadlock between unsuccessful client reconnecting and stopping.




---


[GitHub] ignite pull request #4509: IGNITE-9243: G.allGrids() replaced by IgnitionEx....

2018-08-09 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-9243: G.allGrids() replaced by IgnitionEx.allGridsx()



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

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

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

https://github.com/apache/ignite/pull/4509.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 #4509






---


[GitHub] ignite pull request #4490: IGNITE-1905: Fix AssertionError.

2018-08-06 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-1905: Fix AssertionError.



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

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

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

https://github.com/apache/ignite/pull/4490.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 #4490


commit 3b8782f7d0de59fced728a8ac1d74959b326ecfb
Author: Vitaliy Biryukov 
Date:   2018-08-06T19:10:07Z

IGNITE-1905: Fix AssertionError.




---


[GitHub] ignite pull request #4477: Cache (Deadlock Detection) suite hangs

2018-08-02 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

Cache (Deadlock Detection) suite hangs



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

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

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

https://github.com/apache/ignite/pull/4477.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 #4477


commit d14e6bbd462f83a3d90323757eebe3d6fc40ecd2
Author: Vitaliy Biryukov 
Date:   2018-08-02T15:29:25Z

IGNITE-9169: Eating IgniteInterruptedCheckedException in thread prevented.




---


[GitHub] ignite pull request #4475: IGNITE-9138: ZookeeperDiscoverySpiTest#checkInter...

2018-08-02 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-9138: ZookeeperDiscoverySpiTest#checkInternalStructuresCleanup fails 
if zk cluster was stpped before nodes.



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

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

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

https://github.com/apache/ignite/pull/4475.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 #4475


commit 2a1a36b5775a3c5573e70cfdaa318824ecea36ef
Author: Vitaliy Biryukov 
Date:   2018-07-31T08:51:51Z

IGNITE-9138: ZookeeperDiscoverySpiTest#checkInternalStructuresCleanup fails 
if zk cluster was stpped before nodes.




---


[GitHub] ignite pull request #4459: IGNITE-9138: ZookeeperDiscoverySpiTest#checkInter...

2018-07-31 Thread BiryukovVA
Github user BiryukovVA closed the pull request at:

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


---


[GitHub] ignite pull request #4461: IGNITE-9134: ZookeeperDiscoverySpiTest#testLargeU...

2018-07-31 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-9134: ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with 
OOME.



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

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

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

https://github.com/apache/ignite/pull/4461.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 #4461


commit c430a34c477e5c2b0f60a34335277910c5982691
Author: Vitaliy Biryukov 
Date:   2018-07-31T12:46:25Z

IGNITE-9134: ZookeeperDiscoverySpiTest#testLargeUserAttribute3 fails with 
OOME.




---


[GitHub] ignite pull request #4459: IGNITE-9130: ZookeeperDiscoverySpiTest#checkInter...

2018-07-31 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-9130: ZookeeperDiscoverySpiTest#checkInternalStructuresCleanup fails 
if zk cluster was stpped before nodes.



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

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

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

https://github.com/apache/ignite/pull/4459.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 #4459


commit 263bcea8b83c56f883e046e40139362f419c8252
Author: Vitaliy Biryukov 
Date:   2018-07-31T08:45:17Z

IGNITE-9130: ZookeeperDiscoverySpiTest#checkInternalStructuresCleanup fails 
if zk cluster was stpped before nodes.




---


[GitHub] ignite pull request #4458: IGNITE-9130: Test fixed.

2018-07-30 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-9130: Test fixed.



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

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

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

https://github.com/apache/ignite/pull/4458.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 #4458


commit d077e8c0af3ee2a7c3d5cef41005b451c205a708
Author: Vitaliy Biryukov 
Date:   2018-07-30T16:48:42Z

IGNITE-9130: Test fixed.




---


[GitHub] ignite pull request #4450: fix timeout.

2018-07-28 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

fix timeout.



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

$ git pull https://github.com/BiryukovVA/ignite timeout_zk_suite

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

https://github.com/apache/ignite/pull/4450.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 #4450


commit e8a8dbd34a68b267b217d86e958962193d899146
Author: Vitaliy Biryukov 
Date:   2018-07-27T10:03:19Z

fix timeout.




---


[GitHub] ignite pull request #4169: GNITE-8699: For TC.

2018-06-21 Thread BiryukovVA
Github user BiryukovVA closed the pull request at:

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


---


[GitHub] ignite pull request #4192: IGNITE-8182: TC.

2018-06-14 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-8182: TC.



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

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

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

https://github.com/apache/ignite/pull/4192.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 #4192


commit 4fc90a7146eb7271bbf7edbe350fb027908a96ee
Author: Vitaliy Biryukov 
Date:   2018-06-14T18:24:48Z

IGNITE-8182: TC.




---


[GitHub] ignite pull request #4177: IGNITE-8179: Fluky test.

2018-06-09 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-8179: Fluky test.



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

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

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

https://github.com/apache/ignite/pull/4177.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 #4177


commit 543d6af8c3a458700fda6b2958de2634e14c2707
Author: Vitaliy Biryukov 
Date:   2018-06-09T17:38:12Z

GNITE-8179: Test fixed.

commit 0a25439bc1d79bc2edfc1fab15d68f33999685ad
Author: Vitaliy Biryukov 
Date:   2018-06-09T17:41:59Z

GNITE-8179: For TC testing.




---


[GitHub] ignite pull request #4169: GNITE-8699: For TC.

2018-06-09 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

GNITE-8699: For TC.



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

$ git pull https://github.com/BiryukovVA/ignite IGNITE_8699_TC

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

https://github.com/apache/ignite/pull/4169.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 #4169


commit 740bd7b8a096c7b90051df235c2c4fc52ed7b53a
Author: Vitaliy Biryukov 
Date:   2018-06-09T11:27:27Z

GNITE-8699: For TC.




---


[GitHub] ignite pull request #4161: GNITE-8699: Flaky test.

2018-06-08 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

GNITE-8699: Flaky test.



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

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

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

https://github.com/apache/ignite/pull/4161.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 #4161


commit 709ae0f6d914c7cb99ce8b637a75c7fbba1a951a
Author: Vitaliy Biryukov 
Date:   2018-06-08T21:37:39Z

GNITE-8699: Flaky test.




---


[GitHub] ignite pull request #4067: graceful shutdown test

2018-05-24 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

graceful shutdown test



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

$ git pull https://github.com/BiryukovVA/ignite graceful_shutdown_test

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

https://github.com/apache/ignite/pull/4067.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 #4067


commit c236caf256ab49c0b7ae3de06702c6f41f3b7ef6
Author: Vitaliy Biryukov <biryukovvitaliy92@...>
Date:   2018-05-24T22:47:23Z

test




---


[GitHub] ignite pull request #3820: IGNITE-8257: GridFutureAdapterSelfTest#testChaini...

2018-04-13 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-8257: GridFutureAdapterSelfTest#testChaining fixed.



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

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

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

https://github.com/apache/ignite/pull/3820.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 #3820


commit 7a2fe2b4a7d82b742f308936981149a4182a
Author: Vitaliy Biryukov <biryukovvitaliy92@...>
Date:   2018-04-13T15:14:27Z

IGNITE-8257: Test fixed.




---


[GitHub] ignite pull request #3747: IGNITE-5978

2018-04-04 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-5978

Test fixed.

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

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

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

https://github.com/apache/ignite/pull/3747.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 #3747


commit 7ad83373fe097d97fdfc1d6abc1948d1f263d97a
Author: Vitaliy Biryukov <biryukovvitaliy92@...>
Date:   2018-04-04T10:50:08Z

IGNITE-5978: Test fixed.




---


[GitHub] ignite pull request #3659: IGNITE-7986: GridPartitionStateMap.entrySet() opt...

2018-03-19 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-7986: GridPartitionStateMap.entrySet() optimization.



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

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

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

https://github.com/apache/ignite/pull/3659.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 #3659


commit 255ea51a96a0c1b6ce36d189dc670f4bb9c54010
Author: Vitaliy Biryukov <biryukovvitaliy92@...>
Date:   2018-03-19T13:47:01Z

IGNITE-7986: GridPartitionStateMap.entrySet() optimization.




---


[GitHub] ignite pull request #3250: IGNITE-3464

2017-12-18 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-3464

Fixed bug - race between partition exchange and prepare/finish requests.

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

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

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

https://github.com/apache/ignite/pull/3250.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 #3250


commit a370e2f30008b244f26fcdda0eb0a30e8132f04a
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-12-18T23:15:24Z

IGNITE-3464: Fixed bug - race between partition exchange and prepare/finish 
requests.




---


[GitHub] ignite pull request #3180: IGNITE-6224: Waiting TX completion on node stop.

2017-12-08 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-6224: Waiting TX completion on node stop.



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

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

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

https://github.com/apache/ignite/pull/3180.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 #3180


commit b2268dcfecde365e3afee45b7a3c5bf7efe56d29
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-12-08T11:23:19Z

IGNITE-6224: Waiting TX completion on node stop.




---


[GitHub] ignite pull request #3033: IGNITE-6527: Solution 2.

2017-11-14 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-6527: Solution 2.



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

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

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

https://github.com/apache/ignite/pull/3033.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 #3033


commit dc6e337c4663e977abd1c56e60837a9335f26215
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-11-14T12:58:58Z

IGNITE-6527: Example solution 2.




---


[GitHub] ignite pull request #3032: IGNITE-6445: Solution 1.

2017-11-14 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-6445: Solution 1.



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

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

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

https://github.com/apache/ignite/pull/3032.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 #3032


commit 262f6ab020a067f6e3982ac6073b3781b59d7615
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-10-03T13:41:18Z

IGNITE-6445: Bug fixed.




---


[GitHub] ignite pull request #2803: IGNITE-6557: Fluky test fixed.

2017-10-04 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-6557: Fluky test fixed.



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

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

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

https://github.com/apache/ignite/pull/2803.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 #2803


commit bf9b21f898ffc847d3253669e463ef44e536156c
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-10-04T16:57:39Z

IGNITE-6557: Fluky test fixed.




---


[GitHub] ignite pull request #2796: IGNITE-5504: Fluky test fixed.

2017-10-03 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-5504: Fluky test fixed.



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

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

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

https://github.com/apache/ignite/pull/2796.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 #2796


commit 23a18d2cf8ab1da0739c54e729fddc0cd30f3c3d
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-10-03T13:49:51Z

IGNITE-5504: Fluky test fixed.




---


[GitHub] ignite pull request #2743: IGNITE-6445_txLocksInfo

2017-09-25 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-6445_txLocksInfo



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

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

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

https://github.com/apache/ignite/pull/2743.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 #2743


commit 14611563724432e87ea64683af35c38b99e766ed
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-19T15:39:40Z

IGNITE-6442: Bug fixed.

commit 0b6c87d097a180820dcf14fcbd9f48be39b24911
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-22T08:08:26Z

IGNITE-6442: Bug fixed in another way.

commit e5433647354ef90571207ca6faef53f768e06fe3
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-24T23:22:34Z

IGNITE-6442: Refactoring.

commit 65cb5c17035106a52cec31a08ac6983193bb6adc
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-25T15:13:07Z

IGNITE-6442: fixed test.

commit e812122bed19488df3dd3c6345772841b39b754c
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-25T16:40:16Z

IGNITE-6445: Bug fixed.

commit 5f50c13ed6a8bf6f2370a51711ea8ab00b2a40b2
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-25T16:41:09Z

Merge branch 'IGNITE-6442' into IGNITE-6445_txLocksInfo

commit 6a51e0dd814043991c5d806b3c66503fc37206f9
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-25T16:43:02Z

IGNITE-6445: Test.




---


[GitHub] ignite pull request #2699: IGNITE-6442

2017-09-19 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-6442



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

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

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

https://github.com/apache/ignite/pull/2699.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 #2699


commit b2ee52f335c02211b3c26aab3eae708b6fe09cd9
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-19T15:39:40Z

IGNITE-6442: Bug fixed.




---


[GitHub] ignite pull request #2592: Fixed wrong partitioning.

2017-09-04 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

Fixed wrong partitioning.



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

$ git pull https://github.com/BiryukovVA/ignite TestPessimisticDD

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

https://github.com/apache/ignite/pull/2592.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 #2592


commit 0812b99ce56da3846b6f7cf3363aae63bb3cf87c
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-04T22:07:56Z

Fixed wrong partitioning.




---


[GitHub] ignite pull request #2415: IGNITE-5865: Test fixed.

2017-09-04 Thread BiryukovVA
GitHub user BiryukovVA reopened a pull request:

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

IGNITE-5865: Test fixed.



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

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

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

https://github.com/apache/ignite/pull/2415.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 #2415


commit aedf1ca7dd9b71c923aba4254b93a9055c55bf22
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-09-04T15:29:19Z

IGNITE-5865: Fixed wrong partitioning.




---


[GitHub] ignite pull request #2415: IGNITE-5865: Test fixed.

2017-09-04 Thread BiryukovVA
Github user BiryukovVA closed the pull request at:

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


---


[GitHub] ignite pull request #2415: IGNITE-5865: Test fixed.

2017-08-08 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-5865: Test fixed.



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

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

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

https://github.com/apache/ignite/pull/2415.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 #2415


commit af94f2708c93e9a904f3dac65638f297c93e5543
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-08-08T17:29:21Z

IGNITE-5865: Test fixed.




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] ignite pull request #2355: IGNITE-5859: Utils.ceilPow2 method fixed.

2017-07-27 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-5859: Utils.ceilPow2 method fixed.



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

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

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

https://github.com/apache/ignite/pull/2355.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 #2355


commit b2c4c01d8bccc55532de276cdca24ab23680fcc6
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-07-27T17:38:08Z

IGNITE-5859: Utils.ceilPow2 method fixed.




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] ignite pull request #2322: IGNITE-3950: Issue is not reproduce.

2017-07-19 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

IGNITE-3950: Issue is not reproduce.



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

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

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

https://github.com/apache/ignite/pull/2322.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 #2322


commit 51368ffa65259e2f449aeaf04c2189f12139a629
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-07-19T13:29:36Z

IGNITE-3950: Issue is not reproduce.




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] ignite pull request #2279: Merge remote-tracking branch 'upstream/master' in...

2017-07-11 Thread BiryukovVA
GitHub user BiryukovVA opened a pull request:

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

Merge remote-tracking branch 'upstream/master' into IGNITE-5452

IGNITE-5452:
1) Handled eaten InterruptedException in TimeoutObject.
2) Test correctness of rollback a transaction with timeout during the grid 
stop.


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

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

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

https://github.com/apache/ignite/pull/2279.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 #2279


commit b2be98aff13d239dc0999491ebde52bd450a0bd0
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-07-11T13:06:10Z

IGNITE-5452:
1) Handled eaten InterruptedException in TimeoutObject.
2) Test correctness of rollback a transaction with timeout during the grid 
stop.

commit e663bb37d86dfb4e6a57ba95629d2635e4cb92cc
Author: Vitaliy Biryukov <biryukovvitali...@gmail.com>
Date:   2017-07-11T13:09:00Z

Merge remote-tracking branch 'upstream/master' into IGNITE-5452




---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


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

2017-06-26 Thread BiryukovVA
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 <ali-2...@mail.ru>
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 <ali-2...@mail.ru>
Date:   2017-06-26T11:17:10Z

IGNITE-5468: Refactoring.

commit 08734b11c7456aee6292ecc3b0778a8187fe76a4
Author: Vitaliy <ali-2...@mail.ru>
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 <ali-2...@mail.ru>
Date:   2017-06-26T11:17:10Z

IGNITE-5468: Refactoring.

commit 2aa81f94b31c94efde0ad7d765bd4a70cb486e32
Author: Vitaliy <ali-2...@mail.ru>
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---