[GitHub] ignite pull request #1490: Ignite 4541

2017-02-02 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1490 Ignite 4541 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4541 Alternatively you can review and apply

[GitHub] ignite pull request #1497: Ignite 4541b

2017-02-03 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1497 Ignite 4541b You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4541b Alternatively you can review and apply

[GitHub] ignite pull request #1503: Ignite yyyy

2017-02-07 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1503 Ignite You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite- Alternatively you can review and apply

[GitHub] ignite pull request #1579: Ignite 4755

2017-02-27 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1579 Ignite 4755 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4755 Alternatively you can review and apply

[GitHub] ignite pull request #1589: Ignite 4541c

2017-03-02 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1589 Ignite 4541c You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4541c Alternatively you can review and apply

[GitHub] ignite pull request #1610: Ignite 4813

2017-03-10 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1610 Ignite 4813 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4813 Alternatively you can review and apply

[GitHub] ignite pull request #1678: Ignite 1925

2017-03-27 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1678 Ignite 1925 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1925 Alternatively you can review and apply

[GitHub] ignite pull request #1706: Ignite 4862

2017-03-30 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1706 Ignite 4862 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4862 Alternatively you can review and apply

[GitHub] ignite pull request #1901: Ignite 4862 mux

2017-05-03 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1901 Ignite 4862 mux You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4862-mux Alternatively you can review and

[GitHub] ignite pull request #1928: Ignite 5193

2017-05-11 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1928 Ignite 5193 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5193 Alternatively you can review and apply

[GitHub] ignite pull request #1946: Ignite 5131

2017-05-15 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1946 Ignite 5131 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5131 Alternatively you can review and apply

[GitHub] ignite pull request #1966: Ignite 5168

2017-05-17 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1966 Ignite 5168 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5168 Alternatively you can review and apply

[GitHub] ignite pull request #2002: Ignite 5267

2017-05-24 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/2002 Ignite 5267 You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/ignite ignite-5267 Alternatively you can review and apply these

[GitHub] ignite pull request #2084: Ignite 5410

2017-06-05 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/2084 Ignite 5410 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-5410 Alternatively you can review and apply

[GitHub] ignite pull request: Ignite 1632

2016-03-31 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/590 Ignite 1632 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1632 Alternatively you can review and apply these

[GitHub] ignite pull request: Ignite 1679b

2016-04-05 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/605 Ignite 1679b You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1679b Alternatively you can review and apply

[GitHub] ignite pull request: Ignite 2101

2016-04-05 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/609 Ignite 2101 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2101 Alternatively you can review and apply these

[GitHub] ignite pull request: Ignite 2115

2016-04-06 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/615 Ignite 2115 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2115 Alternatively you can review and apply these

[GitHub] ignite pull request: Ignite 2354

2016-04-07 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/622 Ignite 2354 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2354 Alternatively you can review and apply these

[GitHub] ignite pull request: Ignite 2966

2016-04-08 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/626 Ignite 2966 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2966 Alternatively you can review and apply these

[GitHub] ignite pull request: Ignite 2725

2016-04-08 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/627 Ignite 2725 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2725 Alternatively you can review and apply these

[GitHub] ignite pull request: Ignite 1743b

2016-04-29 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/678 Ignite 1743b IGNITE-1743 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1743b Alternatively you can review and

[GitHub] ignite pull request #787: Ignite 3285 -- merge to Ignite

2016-06-09 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/787 Ignite 3285 -- merge to Ignite You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3285 Alternatively you can

[GitHub] ignite pull request #792: Ignite 2938b

2016-06-10 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/792 Ignite 2938b You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2938b Alternatively you can review and apply

[GitHub] ignite pull request #793: Ignite 2938

2016-06-10 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/793 Ignite 2938 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2938 Alternatively you can review and apply

[GitHub] ignite pull request #810: Ignite 3184

2016-06-16 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/810 Ignite 3184 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-3184 Alternatively you can review and apply these

[GitHub] ignite pull request #818: Ignite 3184

2016-06-20 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/818 Ignite 3184 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3184 Alternatively you can review and apply

[GitHub] ignite pull request #834: Ignite 3185

2016-06-27 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/834 Ignite 3185 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3185 Alternatively you can review and apply

[GitHub] ignite pull request #845: Ignite 3405

2016-07-01 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/845 Ignite 3405 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3405 Alternatively you can review and apply

[GitHub] ignite pull request #859: Ignite 3414 tests

2016-07-07 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/859 Ignite 3414 tests ignite-3414-tests, PRQ for tests . You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3414

[GitHub] ignite pull request #860: Gridgain 7.5.29 p1

2016-07-07 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/860 Gridgain 7.5.29 p1 for public TC tests You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite gridgain-7.5.29-p1

[GitHub] ignite pull request #896: Ignite 1.6.3 3343

2016-07-26 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/896 Ignite 1.6.3 3343 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.6.3-3343 Alternatively you can review

[GitHub] ignite pull request #899: Ignite 1.6.3 1637

2016-07-26 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/899 Ignite 1.6.3 1637 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.6.3-1637 Alternatively you can review

[GitHub] ignite pull request #47: Ignite 1298 flush

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/47 --- 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

[GitHub] ignite pull request #89: ignite-1465: provided more detailed error massage i...

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/89 --- 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

[GitHub] ignite pull request #91: Ignite 1392

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/91 --- 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

[GitHub] ignite pull request #92: ignite-1477: more detailed error messages.

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/92 --- 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

[GitHub] ignite pull request #93: IG-1376: fixed.

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/93 --- 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

[GitHub] ignite pull request #98: Ignite 586

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/98 --- 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

[GitHub] ignite pull request #101: IGNITE-586: version for "master" branch

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/101 --- 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

[GitHub] ignite pull request #105: Ignite 1515 b

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/105 --- 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

[GitHub] ignite pull request #115: IGNITE-1573: mkdirs concurrency fixed.

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/115 --- 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

[GitHub] ignite pull request #141: Ignite 1590

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/141 --- 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

[GitHub] ignite pull request #156: IGNITE-1487: exceptions on normal execution path a...

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/156 --- 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

[GitHub] ignite pull request #157: ignite-825: disabled test remastered and restored.

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/157 --- 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

[GitHub] ignite pull request #168: Ignite 1740

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/168 --- 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

[GitHub] ignite pull request #168: Ignite 1740

2016-08-08 Thread iveselovskiy
GitHub user iveselovskiy reopened a pull request: https://github.com/apache/ignite/pull/168 Ignite 1740 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1740 Alternatively you can review and apply

[GitHub] ignite pull request #168: Ignite 1740

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/168 --- 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

[GitHub] ignite pull request #198: IGNITE-1850.

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/198 --- 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

[GitHub] ignite pull request #225: ignite-183: IgfsImpl and IgfsMetaManager use the s...

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/225 --- 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

[GitHub] ignite pull request #240: ignite-1639

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/240 --- 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

[GitHub] ignite pull request #277: Ignite 1926

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/277 --- 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

[GitHub] ignite pull request #350: IG-2195: trial.

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/350 --- 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

[GitHub] ignite pull request #360: 2206

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/360 --- 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

[GitHub] ignite pull request #361: ignite-2218: deleted HadoopNativeCodeLoader

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/361 --- 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

[GitHub] ignite pull request #363: Ignite tmp

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/363 --- 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

[GitHub] ignite pull request #373: Ignite igfs kerberos

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/373 --- 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

[GitHub] ignite pull request #401: TESTING BRANCH, DO NOT MERGE Ignite 2343 temp do n...

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/401 --- 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

[GitHub] ignite pull request #540: Hunk perf 1119

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/540 --- 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

[GitHub] ignite pull request #545: Hunk perf 1119 plus lock relax

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/545 --- 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

[GitHub] ignite pull request #787: Ignite 3285 -- merge to Ignite

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/787 --- 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

[GitHub] ignite pull request #818: Ignite 3184

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/818 --- 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

[GitHub] ignite pull request #793: Ignite 2938

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/793 --- 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

[GitHub] ignite pull request #834: Ignite 3185

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/834 --- 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

[GitHub] ignite pull request #845: Ignite 3405

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/845 --- 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

[GitHub] ignite pull request #859: Ignite 3414 tests

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/859 --- 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

[GitHub] ignite pull request #860: Gridgain 7.5.29 p1

2016-08-08 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/860 --- 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

[GitHub] ignite pull request #1044: Ignite 3775

2016-09-07 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1044 Ignite 3775 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3775 Alternatively you can review and apply

[GitHub] ignite pull request #1053: Ignite 481

2016-09-09 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1053 Ignite 481 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-481 Alternatively you can review and apply

[GitHub] ignite pull request #1077: Ignite 3920

2016-09-16 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1077 Ignite 3920 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3920 Alternatively you can review and apply

[GitHub] ignite pull request #1079: Ignite 3922

2016-09-16 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1079 Ignite 3922 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3922 Alternatively you can review and apply

[GitHub] ignite pull request #1098: Ignite 3943

2016-09-21 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1098 Ignite 3943 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3943 Alternatively you can review and apply

[GitHub] ignite pull request #1103: Ignite 1.6.8 hadoop

2016-09-22 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1103 Ignite 1.6.8 hadoop You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-1.6.8-hadoop Alternatively you can

[GitHub] ignite pull request #1129: Ignite 3998

2016-09-28 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1129 Ignite 3998 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3998 Alternatively you can review and apply

[GitHub] ignite pull request #1228: Ignite 4208

2016-11-10 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1228 Ignite 4208 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4208 Alternatively you can review and apply

[GitHub] ignite pull request #1302: Ignite 4341

2016-11-30 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1302 Ignite 4341 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4341 Alternatively you can review and apply

[GitHub] ignite pull request #1310: IGNITE-4355: (1) double checked locking in Hadoop...

2016-12-02 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1310 IGNITE-4355: (1) double checked locking in HadoopShuffle, (2) lazy co… …ntext init in HadoopShuffleJob. You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #1320: Ignite 3966

2016-12-06 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1320 Ignite 3966 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3966 Alternatively you can review and apply

[GitHub] ignite pull request #1321: Ignite 4341 master2

2016-12-06 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1321 Ignite 4341 master2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4341-master2 Alternatively you can

[GitHub] ignite pull request #1327: Ignite 4386

2016-12-07 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1327 Ignite 4386 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4386 Alternatively you can review and apply

[GitHub] ignite pull request #1335: Ignite 4341 4386

2016-12-08 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1335 Ignite 4341 4386 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4341-4386 Alternatively you can review

[GitHub] ignite pull request #1397: Ignite 4515

2016-12-30 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1397 Ignite 4515 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4515 Alternatively you can review and apply

[GitHub] ignite pull request #1409: Ignite 4219

2017-01-09 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1409 Ignite 4219 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4219 Alternatively you can review and apply

[GitHub] ignite pull request #1416: Ignite 4503

2017-01-10 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1416 Ignite 4503 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-4503 Alternatively you can review and apply

[GitHub] ignite pull request #1420: Ignite 3543

2017-01-11 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1420 Ignite 3543 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3543 Alternatively you can review and apply

[GitHub] ignite pull request #1421: Ignite 3542

2017-01-11 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/1421 Ignite 3542 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-3542 Alternatively you can review and apply

[GitHub] ignite pull request: Ignite 1277 main

2015-08-25 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/34 Ignite 1277 main 1) enabled data cache backups for IGFS to provide data resilience. 2) added tests to check the failovers with backups. You can merge this pull request into a Git

[GitHub] ignite pull request: Ignite 1277 main

2015-08-26 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/34 --- 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

[GitHub] ignite pull request: IGNITE-1299: retry file meta unlock transacti...

2015-08-26 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/39 IGNITE-1299: retry file meta unlock transactions introduced. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite

[GitHub] ignite pull request: Ignite 1298 flush

2015-08-28 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/47 Ignite 1298 flush You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1298-flush Alternatively you can review and

[GitHub] ignite pull request: IGNITE-1299: retry file meta unlock transacti...

2015-08-28 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/39 --- 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

[GitHub] ignite pull request: ignite-1465: provided more detailed error mas...

2015-09-14 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/89 ignite-1465: provided more detailed error massage if config path cann… …ot be resolved. You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request: Ignite 1392

2015-09-14 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/91 Ignite 1392 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1392 Alternatively you can review and apply these

[GitHub] ignite pull request: ignite-1477: more detailed error messages.

2015-09-14 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/92 ignite-1477: more detailed error messages. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1477 Alternatively

[GitHub] ignite pull request: IG-1376: fixed.

2015-09-15 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/93 IG-1376: fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1376 Alternatively you can review and apply

[GitHub] ignite pull request: Ignite 586

2015-09-17 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/98 Ignite 586 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-586 Alternatively you can review and apply these

[GitHub] ignite pull request: IGNITE-586: version for "master" branch

2015-09-18 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/101 IGNITE-586: version for "master" branch You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-

[GitHub] ignite pull request: Ignite 1515 b

2015-09-24 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/105 Ignite 1515 b https://issues.apache.org/jira/browse/IGNITE-1515 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite

[GitHub] ignite pull request: IGNITE-1573: mkdirs concurrency fixed.

2015-09-30 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/115 IGNITE-1573: mkdirs concurrency fixed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1573 Alternatively you

[GitHub] ignite pull request: Ignite 1590

2015-10-07 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/141 Ignite 1590 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1590 Alternatively you can review and apply these

  1   2   >