[jira] [Created] (IGNITE-13561) Fix non-stable test for dynamic indexing

Maksim Timonin created IGNITE-13561: --- Summary: Fix non-stable test for dynamic indexing Key: IGNITE-13561 URL: https://issues.apache.org/jira/browse/IGNITE-13561 Project: Ignite Issue

Migration of spring-data modules to ignite-extensions

Igniters, I propose to migrate spring-data modules from ignite main repository to ignite-extensions. Are there any objections? I've created ticket [1] and PR to both ignite [2] and ignite-extensions [3] repositories. [1] - https://issues.apache.org/jira/browse/IGNITE-13559 [2] -

Broken test in master: BasicIndexTest

Hi, Igniters! I was discovering how indexes work and found a failed test. BasicIndexTest#testInlineSizeChange is broken in master and it's not a flaky case [1]. But it has been failing since 25/09 only. I discovered that it happened after the IGNITE-13207 ticket merged (Checkpointer code

Introduction

Hello Ignite Community! My name is Bojidar Marinov. I have used Apache Ignite for the past few months, and I would like to contribute to it starting with issue IGNITE-13563, my JIRA username being bojidar-bg. I have already submitted a patch, and reviews would be welcome. BRs, Bojidar

[MTCGA]: new failures in builds [5647896] needs to be handled

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master MVCC Cache 7 https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_MvccCache7?branch=%3Cdefault%3E No changes in the build -

[jira] [Created] (IGNITE-13563) Deserializing IBinaryObject containing an IBinaryObject field fails

Bojidar Marinov created IGNITE-13563: Summary: Deserializing IBinaryObject containing an IBinaryObject field fails Key: IGNITE-13563 URL: https://issues.apache.org/jira/browse/IGNITE-13563

Re: [MTCGA]: new failures in builds [5643882] needs to be handled

Folks, Should we also reopen the issue [1] since the change has been reverted? Should we not only merge the changes to the master branch but also cherry-pick them to the ignite-2.9 branch since docs are related to 2.9 release? [1] https://issues.apache.org/jira/browse/IGNITE-7595 On Thu, 8 Oct

Re: Using deprecated active() and unhelpful message in console

Yeah, I suppose a ticket has been filed. I bet it's https://issues.apache.org/jira/browse/IGNITE-13534. Anyway the change looks really good, let's go on! Ilya, it's your turn. -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Created] (IGNITE-13562) Prototype dynamic configuration

Anton Kalashnikov created IGNITE-13562: -- Summary: Prototype dynamic configuration Key: IGNITE-13562 URL: https://issues.apache.org/jira/browse/IGNITE-13562 Project: Ignite Issue Type:

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

@Alex Plehanov , If it still makes sense and not too late, you can cherry-pick the commit with the new docs into the 2.9 branch: https://github.com/apache/ignite/commit/073488ac97517bbaad9f6b94b781fc404646f191 Anyway, it's not crucial as long as we agreed to make an exception for this release.

Re: [MTCGA]: new failures in builds [5643882] needs to be handled

Folks, Apologize for the disruption. The message didn't appear in my inbox even when you CC-ed me directly. I was notified about the issue only today. Anyway, the licensing issue is fixed and the commit is back to the master. Speaking of the process, it can't be 100% the same for tech docs

Re: Using deprecated active() and unhelpful message in console

Great observations! Did you open a ticket? Are you interested in contributing a patch? > On 8 Oct 2020, at 05:41, Ilya Kazakov wrote: > > Hello! > > As a new user of Ignite I faced this problem. When cluster started in > INACTIVE state in logs writes uninformative message: > Ignite

Using deprecated active() and unhelpful message in console

Hello! As a new user of Ignite I faced this problem. When cluster started in INACTIVE state in logs writes uninformative message: >>> Ignite cluster is not active (limited functionality available). Use control.(sh|bat) script or IgniteCluster interface to activate. This message contains two

[jira] [Created] (IGNITE-13557) Logging improvements for PDS memory restore process

Sergey Chugunov created IGNITE-13557: Summary: Logging improvements for PDS memory restore process Key: IGNITE-13557 URL: https://issues.apache.org/jira/browse/IGNITE-13557 Project: Ignite

[jira] [Created] (IGNITE-13559) Migrate spring-data modules to ignite-extensions.

Mikhail Petrov created IGNITE-13559: --- Summary: Migrate spring-data modules to ignite-extensions. Key: IGNITE-13559 URL: https://issues.apache.org/jira/browse/IGNITE-13559 Project: Ignite

[jira] [Created] (IGNITE-13558) GridCacheProcessor should implement better parallelization when restoring partition states on startup

Sergey Chugunov created IGNITE-13558: Summary: GridCacheProcessor should implement better parallelization when restoring partition states on startup Key: IGNITE-13558 URL:

Re: [MTCGA]: new failures in builds [5643882] needs to be handled

Denis, I've tried to quickly add licenses to the files, but there are simply too many different file types in the change. I reverted the original commit and the dependent one about the continuous query guarantees (which, btw, was merged without ticket name and with a merge commit). Please make

[jira] [Created] (IGNITE-13560) Add cluster node attribute colocated BackupFilter

Maksim Timonin created IGNITE-13560: --- Summary: Add cluster node attribute colocated BackupFilter Key: IGNITE-13560 URL: https://issues.apache.org/jira/browse/IGNITE-13560 Project: Ignite