[GitHub] ignite pull request: Ignite 2308

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

[GitHub] ignite pull request: Ignite 2218b

2015-12-25 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/378 Ignite 2218b You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2218b Alternatively you can review and apply

[GitHub] ignite pull request: Ignite igfs kerberos

2015-12-23 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/373 Ignite igfs kerberos You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-igfs-kerberos Alternatively you can

[GitHub] ignite pull request: Ignite tmp

2015-12-22 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/363 Ignite tmp temp PRQ for proprietary build. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-TMP Alternatively

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

2015-12-21 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/361 ignite-2218: deleted HadoopNativeCodeLoader You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2218 Alternatively

[GitHub] ignite pull request: 2206

2015-12-21 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/360 2206 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2206 Alternatively you can review and apply these changes

[GitHub] ignite pull request: Ignite 2206

2015-12-21 Thread iveselovskiy
Github user iveselovskiy closed the pull request at: https://github.com/apache/ignite/pull/359 --- 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 2206

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

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

2015-12-17 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/350 IG-2195: trial. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-2195 Alternatively you can review and apply

[GitHub] ignite pull request: Ignite 1926

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

[GitHub] ignite pull request: Ignite 1679

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

[GitHub] ignite pull request: Ignite 1510

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

[GitHub] ignite pull request: ignite-1639

2015-11-16 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/240 ignite-1639 You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1639 Alternatively you can review and apply these

[GitHub] ignite pull request: Ignite 481

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

[GitHub] ignite pull request: ignite-183: IgfsImpl and IgfsMetaManager use ...

2015-11-12 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/225 ignite-183: IgfsImpl and IgfsMetaManager use the same busyLock. 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-1788: duplicate checking is removed.

2015-11-11 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/221 IGNITE-1788: duplicate checking is removed. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1788 Alternatively

[GitHub] ignite pull request: IGNITE-1566: fix + new test.

2015-11-10 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/216 IGNITE-1566: fix + new test. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1566 Alternatively you can review

[GitHub] ignite pull request: IGNITE-1850.

2015-11-03 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/198 IGNITE-1850. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1850 Alternatively you can review and apply these

[GitHub] ignite pull request: Ignite 1778

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

[GitHub] ignite pull request: Ignite 1777

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

[GitHub] ignite pull request: Ignite 1743

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

[GitHub] ignite pull request: Ignite 1740

2015-10-20 Thread iveselovskiy
GitHub user iveselovskiy opened 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 these

[GitHub] ignite pull request: ignite-825: disabled test remastered and rest...

2015-10-14 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/157 ignite-825: disabled test remastered and restored. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-825

[GitHub] ignite pull request: IGNITE-1487: exceptions on normal execution p...

2015-10-14 Thread iveselovskiy
GitHub user iveselovskiy opened a pull request: https://github.com/apache/ignite/pull/156 IGNITE-1487: exceptions on normal execution path avoided. You can merge this pull request into a Git repository by running: $ git pull https://github.com/iveselovskiy/ignite ignite-1487

[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

[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 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-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 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: 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-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: 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-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-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 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-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 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 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

<    1   2