Re: Apache Ignite RPM packaging (Stage II)

Copying anything manually to anywhere /usr (excluding /usr/local) is an example of slackwarization that package users and creators try to avoid. > By linux file hierarchy convention, home dir should be in /usr/lib Citation needed! I bet you're interpreting it wrong, since I've listed a random

[GitHub] ignite pull request #3864: IGNITE-8021 Fix test issues

GitHub user ivandasch opened a pull request: https://github.com/apache/ignite/pull/3864 IGNITE-8021 Fix test issues You can merge this pull request into a Git repository by running: $ git pull https://github.com/ivandasch/ignite ignite-8021-test-fix Alternatively you can

Re: Is it time to move forward to JUnit4 (5)?

+100500 for upgrading of JUnit https://developer.ibm.com/dwblog/2017/top-five-reasons-to-use-junit-5-java/ https://stackify.com/junit-5/ On Wed, Apr 18, 2018 at 8:59 PM, Dmitry Pavlov wrote: > Hi Igniters, > > During MTCGA monitoring I’ve discovered a number of issues

[GitHub] ignite pull request #3839: Ignite 6681 .NET: QueryMetrics

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3839 ---

[GitHub] ignite pull request #3866: IGNITE-8192 Print out information on how many nod...

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3866 IGNITE-8192 Print out information on how many nodes left until auto-activation You can merge this pull request into a Git repository by running: $ git pull

Re: Orphaned, duplicate, and main-class tests!

Hello! Most of tests were committed by Semyon Boikov. I hope he can shed some light on the purpose of those. E.g. GridBasicPerformanceTest. -- Ilya Kasnacheev 2018-04-18 16:51 GMT+03:00 Dmitry Pavlov : > Hi Ilya, > > could you please involve authors to this dicussions

Re: Orphaned, duplicate, and main-class tests!

Ilya, what's the reason to create new thread with unreadable history attached? 2018-04-18 17:07 GMT+03:00 Ilya Kasnacheev : > Hello! > > Most of tests were committed by Semyon Boikov. I hope he can shed some > light on the purpose of those. > > E.g.

Re: Is it time to move forward to JUnit4 (5)?

First of all it should be new way for testing without modificaitions in JUnit3-style tests and its base classes. Test would migrate one-by one. If old test is quite stable on 3 and no need to mute it/apply config variations (Parametrized annotation) we could keep it as is for some time. ср, 18

Re: Is it time to move forward to JUnit4 (5)?

I vote for upgrading to JUnit 5. It will entail significant changes in the current testing framework. Dmitriy, do you want to change API of GridCommonAbstractTest or deprecate some methods?

[GitHub] ignite pull request #3865: IGNITE-8302 Reduce test IO consumption in case Di...

GitHub user dspavlov opened a pull request: https://github.com/apache/ignite/pull/3865 IGNITE-8302 Reduce test IO consumption in case Direct IO is enabled, … …fixes flakyness of testPageRecoveryAfterFileCorruption You can merge this pull request into a Git repository by

Re: Is it time to move forward to JUnit4 (5)?

+1 for JUnit5 I suppose we should change\create new not only GridCommonAbstractTest, but also rework GridSpiAbstractTest, GridAbstractTest. ср, 18 апр. 2018 г. в 17:37, Vyacheslav Daradur : > I vote for upgrading to JUnit 5. > > It will entail significant changes in the

Re: Can't run CPP tests locally on linux machine

Igor. I tried to comment unexisted header and got following error: src/teamcity/teamcity_boost.cpp: In constructor ‘JetBrains::TeamcityFormatterRegistrar::TeamcityFormatterRegistrar()’: src/teamcity/teamcity_boost.cpp:72:100: error: invalid new-expression of abstract class type

[GitHub] ignite pull request #3867: -

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/3867 - You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-4756-client-fix Alternatively you can review and apply these

[GitHub] ignite pull request #3868: IGNITE-7968 IgniteAtomicSequence.incrementAndGet ...

GitHub user pvinokurov opened a pull request: https://github.com/apache/ignite/pull/3868 IGNITE-7968 IgniteAtomicSequence.incrementAndGet throws ClusterTopolo… …gyException: Failed to acquire lock for keys You can merge this pull request into a Git repository by running: $

[GitHub] ignite pull request #3862: Ignite-8082 ZK MBean

GitHub user agoncharuk opened a pull request: https://github.com/apache/ignite/pull/3862 Ignite-8082 ZK MBean You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-8082 Alternatively you can review and

Re: Orphaned, duplicate, and main-class tests!

Hello! I've decided to return to this task after a break. Can you please tell me why do we have main-class tests? Such as GridBasicPerformanceTest.class, GridBenchmarkCacheGetLoadTest.class, GridBoundedConcurrentLinkedHashSetLoadTest.class, GridCacheDataStructuresLoadTest.class,

Please add me to contributors

Hi everybody. Please add me to contributors My name is Andrew Medvedev My Jira Id is "andmed" Best Andrew

Can't run CPP tests locally on linux machine

Hello, Igniters. Is there way to run CPP tests locally on linux machine? I'm trying to follow DEVNOTES.txt but doesn't get lucky. 1. `./configure --enable-odbc --enable-tests` [1] I see "rm: cannot remove 'core': Is a directory" Is it OK? 2. `make` [2] I got following error:

Re: Can't run CPP tests locally on linux machine

I think it is better to remove this strong dependency on the exact Boost version at all. I've filed a ticket for that: [1]. [1] - https://issues.apache.org/jira/browse/IGNITE-8310 Best Regards, Igor On Wed, Apr 18, 2018 at 4:20 PM, Nikolay Izhikov wrote: > Hello, Igor. >

[jira] [Created] (IGNITE-8310) CPP: Remove strong dependency on Boost 1.58.0

Igor Sapego created IGNITE-8310: --- Summary: CPP: Remove strong dependency on Boost 1.58.0 Key: IGNITE-8310 URL: https://issues.apache.org/jira/browse/IGNITE-8310 Project: Ignite Issue Type:

[GitHub] ignite pull request #3745: IGNITE-8122 Restore partition in state OWNING

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3745 ---

Re: Can't run CPP tests locally on linux machine

Hi, Nikolay, 1. Yes, it's OK; 2. Well, it is the old issue that we are working only with the specific Boost version (1.58.0). You can try commenting out the following line: #include in teamcity_boost.cpp files to make it working with your version. Best Regards, Igor On Wed, Apr 18, 2018 at

[GitHub] ignite pull request #3751: IGNITE-8143: Modified fetching EXTERNAL_LIBS for ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3751 ---

[GitHub] ignite pull request #3863: IGNITE-8134 fix service deployment from nodes out...

GitHub user dmekhanikov opened a pull request: https://github.com/apache/ignite/pull/3863 IGNITE-8134 fix service deployment from nodes outside of BLT You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[GitHub] ignite pull request #3429: IGNITE-7512: fixed NPE when entry processor remov...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3429 ---

Re: Orphaned, duplicate, and main-class tests!

Hi Ilya, could you please involve authors to this dicussions personally? What git annotate says us about test author? Can I hope you would provide assistance to MakeTC Green in case some returned to CI classes will began to fail? Sincerely, Dmitriy Pavlov ср, 18 апр. 2018 г. в 16:42, Ilya

[GitHub] ignite pull request #3870: IGNITE-8312: Simplified the choice of exception t...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3870 IGNITE-8312: Simplified the choice of exception thrown in pessimistic… … "prepare-after-rollback" scenario. You can merge this pull request into a Git repository by running: $

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

On Tue, Apr 17, 2018 at 4:38 PM, Denis Magda wrote: > Dmitriy, > > We don't want to disable the baseline topology for the scenario discussed > here. The goal is to make it more flexible by triggering the rebalancing in > some circumstances. > > As for the SAFE or AGGRESSIVE

[jira] [Created] (IGNITE-8313) Trace logs enhancement for exchange and affinity calculation

Pavel Kovalenko created IGNITE-8313: --- Summary: Trace logs enhancement for exchange and affinity calculation Key: IGNITE-8313 URL: https://issues.apache.org/jira/browse/IGNITE-8313 Project: Ignite

[GitHub] ignite pull request #2400: Fail tests with issue link

Github user dspavlov closed the pull request at: https://github.com/apache/ignite/pull/2400 ---

[GitHub] ignite pull request #3869: IGNITE-7108 Apache Ignite 2.5 RPM and DEB package...

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/3869 IGNITE-7108 Apache Ignite 2.5 RPM and DEB packages * added package.sh script for automation DEB and RPM packages build * added DEB package build * updated RPM package version to 2.5.0

[jira] [Created] (IGNITE-8311) IgniteClientRejoinTest.testClientsReconnectDisabled causes exchange-worker to terminate via NPE

Andrey Kuznetsov created IGNITE-8311: Summary: IgniteClientRejoinTest.testClientsReconnectDisabled causes exchange-worker to terminate via NPE Key: IGNITE-8311 URL:

Re: [GitHub] ignite pull request #3719: IGNITE-8048 merge query entities for dynamic cach...

Hi, Sorry, I assumed that QueryEntities merge process was always applied (on active or inactive cluster) and that it was responsible for auto creating and populate new indexes and columns on the fly... my fault. Then, in addition to updating CacheConfiguration and QuerySchema, does it do

[GitHub] ignite pull request #3827: IGNITE-8276 : Removed incorrect assertion, fixed ...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3827 ---

[jira] [Created] (IGNITE-8312) .NET: CacheAbstractTransactionalTest.TestTxRollbackOnly failure

Andrey Kuznetsov created IGNITE-8312: Summary: .NET: CacheAbstractTransactionalTest.TestTxRollbackOnly failure Key: IGNITE-8312 URL: https://issues.apache.org/jira/browse/IGNITE-8312 Project:

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

I can suggest an improvement to BaselineWatcher by Pavel. I've added a new version to https://issues.apache.org/jira/browse/IGNITE-8241 comments. Pavel, what do you think? Best Regards, Ivan Rakov On 17.04.2018 20:47, Denis Magda wrote: Thanks, Pavel! Alexey, Ivan, could you check that there

Re: Triggering rebalancing on timeout or manually if the baseline topology is not reassembled

Ivan, I think your version is better, because it handles cases when several nodes are left sequentially, so no needs to shrink baseline for each node left. New version also saves some resources using internal scheduler. 2018-04-18 20:41 GMT+03:00 Ivan Rakov : > I can

[IGNITE-7909]: Java code examples are needed for Spark Data Frames.

If any community members have time, please review the code. Three Java files are attached to the Jira ticket: https://issues.apache.org/jira/browse/IGNITE-7909 The code should be functionally equivalent to the Scala Data Frames code that was shipped in 2.4. Data Frame documentation is here:

Is it time to move forward to JUnit4 (5)?

Hi Igniters, During MTCGA monitoring I’ve discovered a number of issues related to test framework itself. In addition it is not convinient to mute tests on TC, because in branches (e.g. 2.5 and in master) we can’t mute it separately. So some tests, which already fixed are shown as failed in our

Re: [IGNITE-7909]: Java code examples are needed for Spark Data Frames.

Hello, Akmal. I see 3 pull requests attached to the ticket [1], [2], [3]. I see 3 java files attached to the ticket, also. Which changes you want to be reviewed and merge? Please, clarify. Delete all unnecessary pull requests link from the ticket. Add new examples to the tests so we can test it

[GitHub] ignite pull request #3850: IGNITE-8243 Fixed possible memory leak

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3850 ---

[GitHub] ignite pull request #3865: IGNITE-8302 Reduce test IO consumption in case Di...

Github user asfgit closed the pull request at: https://github.com/apache/ignite/pull/3865 ---

Re: [GitHub] ignite pull request #3719: IGNITE-8048 merge query entities for dynamic cach...

Hi, What is the problem being addressed by this change? We do not allow for multiple indexes creation at a time. The only possible way to create an index is CREATE INDEX command when only one index is created. On Tue, Apr 17, 2018 at 10:08 PM, Manu wrote: > Hi! > > I have

Re: Apache Ignite nightly release builds

Great job, Petr! FYI: myget credentials can be found in [1] (PMC only) [1] https://svn.apache.org/repos/private/pmc/ignite/credentials/myget.org On Mon, Apr 16, 2018 at 11:49 AM, Petr Ivanov wrote: > Hi, Igniters! > > > I’m glad to inform that starting today Apache Ignite

[jira] [Created] (IGNITE-8307) Web console: panel with buttons Cancel, Save doesn't float at the bottom of the screen under Safari 11.1

Pavel Konstantinov created IGNITE-8307: -- Summary: Web console: panel with buttons Cancel, Save doesn't float at the bottom of the screen under Safari 11.1 Key: IGNITE-8307 URL:

[jira] [Created] (IGNITE-8308) Sporadic NPE in IgniteAtomicSequenceExample at GridDhtTxPrepareFuture.map

Ksenia Rybakova created IGNITE-8308: --- Summary: Sporadic NPE in IgniteAtomicSequenceExample at GridDhtTxPrepareFuture.map Key: IGNITE-8308 URL: https://issues.apache.org/jira/browse/IGNITE-8308

Re: IEP-18: Transparent Data Encryption

Hi Nikolay, Good rule of thumb here - the more design is discussed prior to implementation, the better. There is no specific definition of well- or ill-defined design, this is more about common sense and our general experience. I would say that minimal set of things to be addressed for most major

Re: MTCGA: IGNITE-7791 and GridDhtPartitionsSingleMessage

Igniters, especially who participated in implementaion of IEP-4. I need your advice. I've prepeared fixes for this flaky test. Can you review my changes [1] and share your thoughts? In my opinion, we should not perform caches info removing from LocalJoinCachesContext captured state on reconnect

[GitHub] ignite pull request #3861: IGNITE-8303: Avoided failure handler invocation w...

GitHub user andrey-kuznetsov opened a pull request: https://github.com/apache/ignite/pull/3861 IGNITE-8303: Avoided failure handler invocation when exchange-worker … …terminates before reconnect. You can merge this pull request into a Git repository by running: $ git pull

Re: Docker deployment with EXTERNAL_LIBS environment variable

Hi Petr, I've mentioned you in the ticket. Is it obvious change so we could apply patch? Or could you advise maintainer/expert here? Sincerely, Dmitriy Pavlov ср, 18 апр. 2018 г. в 7:27, Roman Shtykh : > I had the same problem (pretty common not having -i option) and fixed

[jira] [Created] (IGNITE-8309) Cannot change WAL mode from client node

Ilya Kasnacheev created IGNITE-8309: --- Summary: Cannot change WAL mode from client node Key: IGNITE-8309 URL: https://issues.apache.org/jira/browse/IGNITE-8309 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-8314) Web console: add a new type of reusable loading indicator

Ilya Borisov created IGNITE-8314: Summary: Web console: add a new type of reusable loading indicator Key: IGNITE-8314 URL: https://issues.apache.org/jira/browse/IGNITE-8314 Project: Ignite

Re: Please add me to contributors

Andrew, you're in, enjoy! -- Denis On Wed, Apr 18, 2018 at 5:02 AM, Andrew Medvedev < andrew.y.medve...@gmail.com> wrote: > Hi everybody. > > Please add me to contributors > My name is Andrew Medvedev > My Jira Id is "andmed" > > Best > Andrew >

[GitHub] ignite pull request #3871: IGNITE-8286: ScanQuery ignore setLocal with non l...

GitHub user shroman opened a pull request: https://github.com/apache/ignite/pull/3871 IGNITE-8286: ScanQuery ignore setLocal with non local partition. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shroman/ignite IGNITE-8286