[GitHub] ignite pull request #3549: Test run. config option to use off-heap map inste...

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

[GitHub] ignite pull request #3570: Introduce scala-test profile to hide scalatest-ma...

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

[GitHub] ignite pull request #3582: IGNITE-6868 Concurrency performance fix

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3582 IGNITE-6868 Concurrency performance fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite

[jira] [Created] (IGNITE-7836) ExchangeFuture misses onBaselineTopologyChanged callback when forceReassignment is false

Alexey Goncharuk created IGNITE-7836: Summary: ExchangeFuture misses onBaselineTopologyChanged callback when forceReassignment is false Key: IGNITE-7836 URL: https://issues.apache.org/jira/browse/IGNITE-7836

Re: Ignite | Webconsole Dockerfile unifications

Hi, Denis. I guess I’ll be able to cherry-pick my changes to release tag and use resulting project state to build and create docker images, however that won’t be 100% binary compatible with what was tested and release (uploaded to ASF). Though that must not be a problem currently, and at 2.5

[jira] [Created] (IGNITE-7835) Scala tests appeared in wrong configurations

Nikolay Izhikov created IGNITE-7835: --- Summary: Scala tests appeared in wrong configurations Key: IGNITE-7835 URL: https://issues.apache.org/jira/browse/IGNITE-7835 Project: Ignite Issue

Thin client / Binary protocol: questions

Folks, Designing node.js thin lib (IGNITE-) we have the following questions. Could you please have a look and clarify. Thanks, -Alexey - Supported standard types and their type codes. Are defined in the spec: https://apacheignite.readme.io/docs/binary-client-protocol#data-format But,

Re: Ignite | Webconsole Dockerfile unifications in 2.4

Peter, Thanks for keep automating and improving Ignite build/release environment! Igniters, who can review the changes? However, I guess that it's too late to merge the changes into 2.4 branch which is frozen for merges. Considering this, could you prepare docker as well as cloud images (AWS,

Re: Next Steps: GA Grid: Request to contribute GA library to Apache Ignite

> > Based on Denis' request, I understand that Oleg/Yuri will handle merging > 'pull-request' into main codebase. Exactly, I'm expecting the same. -- Denis On Tue, Feb 27, 2018 at 1:22 PM, techbysample wrote: > Denis, > > Good to hear! I am glad that GA Grid will

[GitHub] ignite pull request #3581: IGNITE-5357 replicated cache reads load balancing...

GitHub user DALukjanenko opened a pull request: https://github.com/apache/ignite/pull/3581 IGNITE-5357 replicated cache reads load balancing was added You can merge this pull request into a Git repository by running: $ git pull https://github.com/DALukjanenko/ignite

[GitHub] ignite pull request #3580: IGNITE-6868 Concurrency performance fix

GitHub user alex-plekhanov opened a pull request: https://github.com/apache/ignite/pull/3580 IGNITE-6868 Concurrency performance fix You can merge this pull request into a Git repository by running: $ git pull https://github.com/alex-plekhanov/ignite ignite-6868-perf-fix

Re: Next Steps: GA Grid: Request to contribute GA library to Apache Ignite

Denis, Good to hear! I am glad that GA Grid will officially become apart of Apache Ignite. Based on Denis' request, I understand that Oleg/Yuri will handle merging 'pull-request' into main codebase. Let me know if there is any action for me to take at this time. Also, Denis, I will be

Re: [TeamCity] DataFrame Examples

I prefer to use existing profile. We have a lot of suites, and it is hard to manage and monitor. вт, 27 февр. 2018 г. в 23:02, Nikolay Izhikov : > I've tested it locally so yes, Spark examples can be tested in Ignite > Examples. > > We need to enable `scala` profile for test

Re: [TeamCity] DataFrame Examples

I've tested it locally so yes, Spark examples can be tested in Ignite Examples. We need to enable `scala` profile for test plan and add `IgniteExamplesSparkSelfTestSuite` to Team City properties. Dmitry, please, give me advice. Should I edit Ignite Examples settings or should I create copy of

Re: [TeamCity] DataFrame Examples

If we can run Scala examples there, then yes. -Val On Tue, Feb 27, 2018 at 11:54 AM, Dmitry Pavlov wrote: > Nikolay, Val, > > Could these examples be tested in standard Ignite Examples test suite? As > far as I know Ignite ML and Ignite IGFS are also tested there. > >

Re: [TeamCity] DataFrame Examples

Nikolay, Val, Could these examples be tested in standard Ignite Examples test suite? As far as I know Ignite ML and Ignite IGFS are also tested there. Sincerely, Dmitriy Pavlov вт, 27 февр. 2018 г. в 22:49, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > Nikolay, > > Spark integration

[GitHub] ignite pull request #3573: IGNITE-7816: DataFrame examples fixed.

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

Re: [TeamCity] DataFrame Examples

Nikolay, Spark integration is not related to Scalar, the only thing they have in common is Scala. I think we should have a separate configuration for ignite-spark module. If anything Spark related is currently in Scalar suite, it should be moved from there. -Val On Tue, Feb 27, 2018 at 3:03 AM,

Re: .NET suite failures

Hi Pavel, yes, you're right. All tests passed. I thought it was because of 'IGNITE-7329 .NET: Thin client: SSL connection implemented' and did not look in the log вт, 27 февр. 2018 г. в 19:22, Pavel Tupitsyn : > Hi Dmitry, > > Thanks for bringing this up. > Please see the

[jira] [Created] (IGNITE-7834) Ignite Queries 2 fail rate is more than 95%: DynamicColumnsAbstractConcurrentSelfTest and its subclasses are flaky

Dmitriy Pavlov created IGNITE-7834: -- Summary: Ignite Queries 2 fail rate is more than 95%: DynamicColumnsAbstractConcurrentSelfTest and its subclasses are flaky Key: IGNITE-7834 URL:

[GitHub] ignite pull request #3579: IGNITE-7467 Partition counters validation

GitHub user Jokser opened a pull request: https://github.com/apache/ignite/pull/3579 IGNITE-7467 Partition counters validation You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-7467 Alternatively you

Re: .NET suite failures

Hi Dmitry, Thanks for bringing this up. Please see the build log, it indicates failed Java build: Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on project ignite-storm: Error resolving project artifact: Could not transfer artifact

[jira] [Created] (IGNITE-7833) Find out possible ways to handle partition update counters inconsistency

Pavel Kovalenko created IGNITE-7833: --- Summary: Find out possible ways to handle partition update counters inconsistency Key: IGNITE-7833 URL: https://issues.apache.org/jira/browse/IGNITE-7833

Re: TeamCity. Ignite RDD tests

Hi Nikolay, IMO you can merge. Just check if following suites work correct and still execute its tests: Ignite Scalar Examples [Scala] Ignite Visor Console [Scala] Sincerely, Dmitriy Pavlov вт, 27 февр. 2018 г. в 19:15, Nikolay Izhikov : > Hello, > > If there are no any

Re: TeamCity. Ignite RDD tests

Hello, If there are no any objections I merge the fix tomorrow. https://github.com/apache/ignite/pull/3570 В Вт, 27/02/2018 в 13:27 +0300, Nikolay Izhikov пишет: > Hello, Alexey, what do you think? > > Let's fix this issue! > > В Пн, 26/02/2018 в 16:29 +, Dmitry Pavlov пишет: > > I

.NET suite failures

Hi Pavel, Igniters, .NET test failed after recent changes https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_IgnitePlatformNet_IgniteTests24Java8=%3Cdefault%3E=buildTypeStatusDiv Failed suites are following: Ignite Platform .NET [ tests 0 TC_EXIT_CODE ] Ignite

[GitHub] ignite pull request #3578: neineighborhoods selection logic was added

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/3578 neineighborhoods selection logic was added You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-5357 Alternatively you

[jira] [Created] (IGNITE-7832) Partition lost events looks broken.

Andrew Mashenkov created IGNITE-7832: Summary: Partition lost events looks broken. Key: IGNITE-7832 URL: https://issues.apache.org/jira/browse/IGNITE-7832 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-7831) Throw Exceptions instead of AssertionErrors when reading from corrupted persistence

Ilya Lantukh created IGNITE-7831: Summary: Throw Exceptions instead of AssertionErrors when reading from corrupted persistence Key: IGNITE-7831 URL: https://issues.apache.org/jira/browse/IGNITE-7831

Re: [IGNITE-5714] Design proposal of suspend/resume for pessimistic tx

Hello, Alexey. Great mail, by the way. I think, it would be great to have this feature in Ignite. > I haven't removed thread id completely from code. Can we remove thread id completely from code? Can you estimate how much effort do we need? As far as I can see from parent task [1] we need some

[jira] [Created] (IGNITE-7830) Adopt kNN model to the new Partitioned Dataset

Aleksey Zinoviev created IGNITE-7830: Summary: Adopt kNN model to the new Partitioned Dataset Key: IGNITE-7830 URL: https://issues.apache.org/jira/browse/IGNITE-7830 Project: Ignite

[jira] [Created] (IGNITE-7828) Adopt yardstick tests for the new version of kNN regression algorithm

Aleksey Zinoviev created IGNITE-7828: Summary: Adopt yardstick tests for the new version of kNN regression algorithm Key: IGNITE-7828 URL: https://issues.apache.org/jira/browse/IGNITE-7828

[jira] [Created] (IGNITE-7829) Adopt kNN regression example to the new Partitioned Dataset

Aleksey Zinoviev created IGNITE-7829: Summary: Adopt kNN regression example to the new Partitioned Dataset Key: IGNITE-7829 URL: https://issues.apache.org/jira/browse/IGNITE-7829 Project: Ignite

[jira] [Created] (IGNITE-7827) Adopt kNN regression to the new Partitioned Dataset

Aleksey Zinoviev created IGNITE-7827: Summary: Adopt kNN regression to the new Partitioned Dataset Key: IGNITE-7827 URL: https://issues.apache.org/jira/browse/IGNITE-7827 Project: Ignite

Re: Stop nodes after test by default - IGNITE-6842

Yep, link may not be correct. Here is correct version: TC: *https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8_IgniteTests24Java8=pull%2F3542%2Fhead * вт, 27 февр.

[GitHub] ignite pull request #3577: IGNITE-7796: Adopt kNN classification example to ...

GitHub user zaleslaw opened a pull request: https://github.com/apache/ignite/pull/3577 IGNITE-7796: Adopt kNN classification example to the new datasets You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite

[jira] [Created] (IGNITE-7826) DStatProbe benchmark empty result output

Burov Ilya created IGNITE-7826: -- Summary: DStatProbe benchmark empty result output Key: IGNITE-7826 URL: https://issues.apache.org/jira/browse/IGNITE-7826 Project: Ignite Issue Type: Bug

Re: Stop nodes after test by default - IGNITE-6842

Hi Maxim, could you please provide link to TC run on your PR? It seems link provided points to run of master. In changes field you may select pull/3542/head before starting RunAll. Igniters, this change is related to our test framework, so change may affect your tests. Please join to review

[GitHub] ignite pull request #3576: Ignite gg 13533

GitHub user dkarachentsev opened a pull request: https://github.com/apache/ignite/pull/3576 Ignite gg 13533 You can merge this pull request into a Git repository by running: $ git pull https://github.com/gridgain/apache-ignite ignite-gg-13533 Alternatively you can review and

[jira] [Created] (IGNITE-7825) ODBC: Update specification documentation

Igor Sapego created IGNITE-7825: --- Summary: ODBC: Update specification documentation Key: IGNITE-7825 URL: https://issues.apache.org/jira/browse/IGNITE-7825 Project: Ignite Issue Type: Task

Re: Stop nodes after test by default - IGNITE-6842

Hi all, I think, I've done with this issue, what should we do next? PR: https://github.com/apache/ignite/pull/3542 Upsource: https://reviews.ignite.apache.org/ignite/review/IGNT-CR-502 TC: https://ci.ignite.apache.org/viewModification.html?modId=723895=false==vcsModificationTests JIRA:

[IGNITE-7789] Ignite Client Nodes testErrorOnDisconnect()

Hi all, I just briefly look at this issue [1] and found that for: 1) CollectionConfiguration[2] we have default backup = 0; 2) AtomicConfiguration[3] we have DFLT_BACKUPS = 1; Is this correct? Because, both of them used for testing dataStructureOperationsTest(). After disconnet and recreation

[GitHub] ignite pull request #3575: IGNITE-7646 OSGI tests fail

GitHub user daradurvs opened a pull request: https://github.com/apache/ignite/pull/3575 IGNITE-7646 OSGI tests fail You can merge this pull request into a Git repository by running: $ git pull https://github.com/daradurvs/ignite ignite-7646 Alternatively you can review and

Ignite | Webconsole Dockerfile unifications in 2.4

Hi, Igniters! In order to correctly process Apache Ignite 2.4 release, I've implemented several changes in Apache Ignite's and Web Console's docker build procedure [1]. My main motivation was to: 1. Unify approach to docker image architecture. Previously, Apache Ignite docker image build

Re: IgniteSet implementation: changes required

As far as I know, Pavel P. is working on fixing existing sets currently. As for {{asSet}} cache adapter, I filed the ticket [1]. [1] https://issues.apache.org/jira/browse/IGNITE-7823 2018-02-27 11:20 GMT+03:00 Vladimir Ozerov : > I think the root issue is that we are

[jira] [Created] (IGNITE-7824) Rollback part of IGNITE-7170 changes

Alexey Popov created IGNITE-7824: Summary: Rollback part of IGNITE-7170 changes Key: IGNITE-7824 URL: https://issues.apache.org/jira/browse/IGNITE-7824 Project: Ignite Issue Type: Bug

[GitHub] ignite pull request #3574: IGNITE-7821 Update Apache Ignite and Web Console ...

GitHub user vveider opened a pull request: https://github.com/apache/ignite/pull/3574 IGNITE-7821 Update Apache Ignite and Web Console Dockerfile for 2.4 version and local build * removed Apache Ignite's Docker module obsolete autobuild directory layout * updated Apache

[jira] [Created] (IGNITE-7823) Enrich IgniteCache with asSet method

Andrey Kuznetsov created IGNITE-7823: Summary: Enrich IgniteCache with asSet method Key: IGNITE-7823 URL: https://issues.apache.org/jira/browse/IGNITE-7823 Project: Ignite Issue Type:

[TeamCity] DataFrame Examples

Hello, Igniters. I've created several examples for a Ignite DataFrame. Currently, they are not tested on Team City. As far as I can understand, they should be checked in "Ignite Scalar Examples [Scala]". But it marked as obsolete [1] Please, give me advice: 1. Should we test Ignite DataFrame

[GitHub] ignite pull request #3573: IGNITE-7816: DataFrame examples fixed.

GitHub user nizhikov opened a pull request: https://github.com/apache/ignite/pull/3573 IGNITE-7816: DataFrame examples fixed. moved to `org.apache.ignite.scalar.examples.spark` package. Minor examples improvements. You can merge this pull request into a Git repository by running:

Re: TeamCity. Ignite RDD tests

Hello, Alexey, what do you think? Let's fix this issue! В Пн, 26/02/2018 в 16:29 +, Dmitry Pavlov пишет: > I agree. > > Alexey K, what do you think? > > Sincerely, > Dmitriy Pavlov > > пн, 26 февр. 2018 г. в 19:17, Nikolay Izhikov : > > > Hello, Dmitriy. > > > >

Re: MTCGA: Tests of the week

Hi Denis, It is not easy to say exact number of tests, because test failures are quite randomized. Correct metric can be obtained from mass 'RunAll' runs, for example, during weekend. In the same time brief estimation gives number of failures around 30-60 per 'RunAll' instead of 60-80 (we don't

[jira] [Created] (IGNITE-7821) Update Apache Ignite and Web Console Dockerfile for 2.4 version and local build

Peter Ivanov created IGNITE-7821: Summary: Update Apache Ignite and Web Console Dockerfile for 2.4 version and local build Key: IGNITE-7821 URL: https://issues.apache.org/jira/browse/IGNITE-7821

[jira] [Created] (IGNITE-7820) Investigate and fix perfromance drop of WAL for default mode

Andrey Gura created IGNITE-7820: --- Summary: Investigate and fix perfromance drop of WAL for default mode Key: IGNITE-7820 URL: https://issues.apache.org/jira/browse/IGNITE-7820 Project: Ignite

Re: IgniteSet implementation: changes required

I think the root issue is that we are trying to mix different cases in a single solution. What is the common usage patterns of sets? 1) Small mostly-read sets - current implementation is ideal for them - everything is available locally, on-heap and in deserialized form 2) Big data sets -

[jira] [Created] (IGNITE-7819) IgniteServiceConfigVariationsFullApiTest must stop services in finally block

Alexey Goncharuk created IGNITE-7819: Summary: IgniteServiceConfigVariationsFullApiTest must stop services in finally block Key: IGNITE-7819 URL: https://issues.apache.org/jira/browse/IGNITE-7819