[GitHub] ignite pull request #5568: IGNITE-10446 control.sh --cache idle_verify fail ...

2018-12-04 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5568 IGNITE-10446 control.sh --cache idle_verify fail with NPE when node l… …eft grid You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #5553: IGNITE-10205 add to utility command - ./control.s...

2018-12-03 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5553 IGNITE-10205 add to utility command - ./control.sh --cache idle_verif… …y --dump abbility to exclude cache from output file You can merge this pull request into a Git repository by running

[GitHub] ignite pull request #5496: IGNITE-9980 Modify ./control.sh --cache idle_veri...

2018-11-24 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5496 IGNITE-9980 Modify ./control.sh --cache idle_verify --dump print to d… …iff mode (user persistant only/user not-persistent only/system only) cache You can merge this pull request

[GitHub] ignite pull request #5476: IGNITE-10323 Contol utility --deactivate on non-a...

2018-11-22 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5476 IGNITE-10323 Contol utility --deactivate on non-activate cluster prod… …use NPE and handler stop nodes You can merge this pull request into a Git repository by running: $ git pull

[GitHub] ignite pull request #5459: IGNITE-8391

2018-11-21 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5459 IGNITE-8391 Removing some WAL history segments leads to WAL rebalance hanging You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #5233: IGNITE-10092 Race in partition state when checkpo...

2018-11-01 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5233 IGNITE-10092 Race in partition state when checkpoint started at the m… …iddle of starts caches You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request #5093: IGNITE-10028

2018-10-26 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5093 IGNITE-10028 Incorrect handling of page on replacement You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg

[GitHub] ignite pull request #5060: IGNITE-9890 Refactor CachePartitionPartialCounter...

2018-10-24 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/5060 IGNITE-9890 Refactor CachePartitionPartialCountersMap#fromCountersMap… …, no need to sort partitions any time it called. You can merge this pull request into a Git repository by running

[GitHub] ignite pull request #4968: IGNITE-9738 Client node can suddenly fail on star...

2018-10-12 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4968 IGNITE-9738 Client node can suddenly fail on start You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9738

[GitHub] ignite pull request #4764: IGNITE-8879 Blinking baseline node sometimes unab...

2018-09-14 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4764 IGNITE-8879 Blinking baseline node sometimes unable to connect to clu… …ster You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #4671: Ignite 9448

2018-09-03 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4671 Ignite 9448 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9448 Alternatively you can review and apply

[GitHub] ignite pull request #4668: Ignite 2.5.1 p13 zk test

2018-09-03 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4668 Ignite 2.5.1 p13 zk test You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p13-zk-test Alternatively

[GitHub] ignite pull request #4661: IGNITE-9448

2018-08-31 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4661 IGNITE-9448 Change ZooKeeper version to 3.4.13 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-9448

[GitHub] ignite pull request #4456: Ignite 2.5.1 p12

2018-07-30 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4456 Ignite 2.5.1 p12 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p12 Alternatively you can review

[GitHub] ignite pull request #4356: IGNITE-8761 WAL fsync at rollover should be async...

2018-07-13 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4356 IGNITE-8761 WAL fsync at rollover should be asynchronous in LOG_ONLY … …and BACKGROUND modes You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request #4355: Ignite 2.5.1 p10

2018-07-13 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4355 Ignite 2.5.1 p10 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p10 Alternatively you can review

[GitHub] ignite pull request #4311: IGNITE-8754

2018-07-05 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4311 IGNITE-8754 Node outside of baseline does not start when service configured You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache

[GitHub] ignite pull request #4286: IGNITE-8898

2018-07-02 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4286 IGNITE-8898 rename command argument '--force' to '--yes' for control.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache

[GitHub] ignite pull request #4283: GG-13963

2018-07-02 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/4283 ---

[GitHub] ignite pull request #4283: GG-13963

2018-06-29 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4283 GG-13963 rename command argument '--force' to '--yes' for control.sh You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #4274: Ignite-2.5.1-p9

2018-06-28 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4274 Ignite-2.5.1-p9 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-2.5.1-p9 Alternatively you can review

[GitHub] ignite pull request #4197: IGNITE-8594

2018-06-15 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4197 IGNITE-8594 Make error messages in validate_indexes command report more informative You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #4188: IGNITE-8761

2018-06-14 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4188 IGNITE-8761 WAL fsync at rollover should be asynchronous in LOG_ONLY and BACKGROUND modes You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #4010: IGNITE-8491

2018-05-17 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/4010 IGNITE-8491 Add JMX flag: Is the node in baseline or not? You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8491

[GitHub] ignite pull request #3045: IGN-8915

2017-11-16 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/3045 IGN-8915 [IGNITE-6922] Class can not undeploy from grid in some specific cases You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain

[GitHub] ignite pull request #2999: Fixed licensed header

2017-11-08 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/2999 Fixed licensed header You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-6737fix Alternatively you can review

[GitHub] ignite pull request #2934: IGNITE-6737

2017-10-26 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/2934 IGNITE-6737 GridDeploymentPerVersionStore retries loading class infinitely You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache

[GitHub] ignite pull request #2882: IGNITE-1793

2017-10-19 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/2882 IGNITE-1793 [Failed Test] IgnitePartitionedCountDownLatchSelfTest.testLatch hangs on TC sometimes You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request #2546: IGNITE-6213

2017-08-30 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/2546 IGNITE-6213 Unexpected setting local deployment owner anyone node You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #2375: Ignite gg 5038 benchmark

2017-08-02 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/2375 Ignite gg 5038 benchmark You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-5038_benchmark Alternatively

[GitHub] ignite pull request #2011: GNITE-5038 BinaryMarshaller might need to use con...

2017-05-26 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/2011 GNITE-5038 BinaryMarshaller might need to use context class loader for deserialization IGNITE-5038 BinaryMarshaller might need to use context class loader for deserialization You can merge

[GitHub] ignite pull request #1964: IGNITE 5212 Allow custom affinity for system cach...

2017-05-23 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/1964 --- 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 #1964: IGNITE 5212 Allow custom affinity for system cach...

2017-05-17 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/1964 IGNITE 5212 Allow custom affinity for system caches You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-5212

[GitHub] ignite pull request #1963: Ignite gg 7170

2017-05-17 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/1963 Ignite gg 7170 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-7170 Alternatively you can review

[GitHub] ignite pull request #1875: Ignite gg 12084 2

2017-04-26 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/1875 Ignite gg 12084 2 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12084_2 Alternatively you can review

[GitHub] ignite pull request #1843: Ignite gg 12084

2017-04-20 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/1843 Ignite gg 12084 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-12084 Alternatively you can review

[GitHub] ignite pull request #1728: IGNITE-4022

2017-04-04 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/1728 IGNITE-4022 IgniteServices soesn't throw an exception if there are no server nodes You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #1001: IGNITE-3601 Read-only optimistic transaction shou...

2016-08-29 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/1001 IGNITE-3601 Read-only optimistic transaction shouldn't throw an excep… …tion if entry version was not changed. Read only serializable transactions are commiting without check. You

[GitHub] ignite pull request #941: IGNITE-3618 - Client can not load data after serve...

2016-08-10 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/941 IGNITE-3618 - Client can not load data after server restarts You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-3618

[GitHub] ignite pull request #934: IGNITE-3138 - IgniteDataStreamer: failures are not...

2016-08-09 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/934 IGNITE-3138 - IgniteDataStreamer: failures are not shown on the strea… …ming side You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #913: IGNITE-3138 - IgniteDataStreamer: failures are not...

2016-08-09 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/913 --- 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 #849: IGNITE-1802

2016-08-03 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/849 --- 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 #798: Ignite 3226

2016-08-03 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/798 --- 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 #825: Gridgain 7.5.27 yardstick

2016-08-03 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/825 --- 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 #913: IGNITE-3138 - IgniteDataStreamer: failures are not...

2016-08-01 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/913 IGNITE-3138 - IgniteDataStreamer: failures are not shown on the strea… …ming side You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #864: Ignite-3055

2016-07-08 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/864 Ignite-3055 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-3055 Alternatively you can review and apply

[GitHub] ignite pull request #849: IGNITE-1802

2016-07-04 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/849 IGNITE-1802 Ignite.countDownLatch() can return null if latch has been already created. You can merge this pull request into a Git repository by running: $ git pull https://github.com

[GitHub] ignite pull request #828: IGNITE-3362

2016-06-24 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/828 IGNITE-3362 Unit test You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-3362 Alternatively you can review and apply

[GitHub] ignite pull request #796: IGNITE-3151 I rework fixation, so that there was n...

2016-06-16 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/796 --- 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 #805: Ignite-2767

2016-06-15 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/805 --- 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 #805: Ignite-2767

2016-06-15 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/805 Ignite-2767 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-2767 Alternatively you can review and apply

[GitHub] ignite pull request #798: Ignite 3226

2016-06-14 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/798 Ignite 3226 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-3226 Alternatively you can review and apply

[GitHub] ignite pull request #776: IGNITE-2616

2016-06-14 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/776 --- 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 #776: IGNITE-2616

2016-06-03 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/776 IGNITE-2616 NonHeap memory usage metrics don't work as expected. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite

[GitHub] ignite pull request #731: IGNITE-2655

2016-06-03 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/731 --- 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 #762: IGNITE-2616

2016-06-03 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/762 --- 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 #773: IGNITE-3226

2016-06-02 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/773 IGNITE-3226 Load test: iteration over cache partitions using scan queries and performing transactions You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request #659: IGNITE-2383

2016-06-02 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/659 --- 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 #667: IGNITE-3040

2016-06-02 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/667 --- 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 #703: IGNITE-3049

2016-06-02 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/703 --- 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 #732: IGNITE-2667

2016-06-02 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/732 --- 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-2616

2016-05-27 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/762 IGNITE-2616 IGNITE-2616 NonHeap memory usage metrics don't work as expected. You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov

[GitHub] ignite pull request: Ignite 3190

2016-05-25 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/755 Ignite 3190 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-3190 Alternatively you can review and apply

[GitHub] ignite pull request: IGNITE-2667

2016-05-19 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/732 IGNITE-2667 Allow to start caches in PRIVATE and ISOLATED deployment modes when BinaryMarshaller is used You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request: IGNITE-2667

2016-05-19 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/718 --- 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-2655

2016-05-19 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/731 IGNITE-2655 AffinityFunction: primary and backup copies in different locations Add affinity backup filter to FairAffinityFunction and RendezvousAffinityFunction You can merge this pull

[GitHub] ignite pull request: IGNITE-2667

2016-05-13 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/718 IGNITE-2667 Allow to start caches in PRIVATE and ISOLATED deployment modes when BinaryMarshaller is used You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request: IGNITE-3049

2016-05-11 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/670 --- 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-3049

2016-05-11 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/703 IGNITE-3049 Yardstick sql load tests should read sql quiers from an external file Merged missing changes. You can merge this pull request into a Git repository by running: $ git

[GitHub] ignite pull request: IGNITE-2383

2016-04-20 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/659 IGNITE-2383 Non-string system properties should be ignored in node attributes and update checker You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request: Ignite 2594

2016-04-18 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/654 Ignite 2594 You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-2594 Alternatively you can review and apply

[GitHub] ignite pull request: IGNITE-2952

2016-04-18 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/653 IGNITE-2952 Add yardstick benchmark for cache load testing Sql queries are generating randomly by QueryEntries now. You can merge this pull request into a Git repository by running

[GitHub] ignite pull request: IGNITE-2952

2016-04-18 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/646 --- 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-2952

2016-04-14 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/646 IGNITE-2952 Add yardstick benchmark for cache load testing Added SQL query operation to benchmark. You can merge this pull request into a Git repository by running: $ git pull https

[GitHub] ignite pull request: IGNITE-2668

2016-04-14 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/588 --- 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-2952

2016-04-14 Thread vldpyatkov
Github user vldpyatkov closed the pull request at: https://github.com/apache/ignite/pull/640 --- 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-2952

2016-04-13 Thread vldpyatkov
GitHub user vldpyatkov opened a pull request: https://github.com/apache/ignite/pull/640 IGNITE-2952 Add yardstick benchmark for cache load testing You can merge this pull request into a Git repository by running: $ git pull https://github.com/vldpyatkov/ignite ignite-2952