Review needed: IGNITE-13102, IgniteCache#isClosed() returns false on server node even if the cache had been closed before.

Hi! Please review the changes. https://issues.apache.org/jira/browse/IGNITE-13102 Thanks! --- Kind Regards, Konstantin Sirotkin

Re: Apache Ignite 3.0

Hi Denis, Val Thank you for your reply and really appreciate it. It will be very cool to be able to connect and plan release together and learn more about Ignite in the process :) Regards Saikat On Thu, Aug 6, 2020 at 7:12 PM Valentin Kulichenko < valentin.kuliche...@gmail.com> wrote: > Hi

Re: Apache Ignite 3.0

Hi Saikat, That surely is a great idea. We will work together with Denis on setting this up in the nearest future. -Val On Thu, Aug 6, 2020 at 10:21 AM Denis Magda wrote: > Saikat, > > Fully support your idea on a virtual meetup! Once Val collects and outlines > the main changes with

Re: Apache Ignite 3.0

Hi Valentin Thank you for sharing and starting the thread. I am thinking if it will be a good idea to have a virtual meet setup to discuss on the release planning. It will help to learn more individual features to be added and also to understand about features that have been deprecated and

[jira] [Created] (IGNITE-13338) Ability to Query for the Names of All Distributed Data Structures

Brandon Szeliga created IGNITE-13338: Summary: Ability to Query for the Names of All Distributed Data Structures Key: IGNITE-13338 URL: https://issues.apache.org/jira/browse/IGNITE-13338 Project:

Re: Apache Ignite 3.0

Saikat, Fully support your idea on a virtual meetup! Once Val collects and outlines the main changes with directions on wiki, we’ll go ahead and schedule the meetup to talk things out in a bit more detail. We’ll use our new Virtual Ignite Meetup group for that inviting both Ignite contributors

Re: [DISCUSSION] Cache warmup

Hi Kirill, Alexey, On the interface structure. So, as a user I'll see one interface, WarmUpConfiguration, with no methods. I choose an implementation and configure it like cfg.setWarmUpConfiguration(new LoadEverythingWarmupConfiguration()); Ignite tries to map the

Re: Moving Ignite documentation to github

Alex, Thanks a lot for preparing the list. It's truly handy. We'll take care of all the unassigned tickets by reaching out to the contributors. - Denis On Thu, Aug 6, 2020 at 4:13 AM Alex Plehanov wrote: > Artem, > > Ok, let's suggest edits for 2.9 release documentations via pull request to

[jira] [Created] (IGNITE-13330) Document java thin client 2.8 and 2.9 release features

Aleksey Plekhanov created IGNITE-13330: -- Summary: Document java thin client 2.8 and 2.9 release features Key: IGNITE-13330 URL: https://issues.apache.org/jira/browse/IGNITE-13330 Project: Ignite

[jira] [Created] (IGNITE-13333) Document TDE master key rotation

Aleksey Plekhanov created IGNITE-1: -- Summary: Document TDE master key rotation Key: IGNITE-1 URL: https://issues.apache.org/jira/browse/IGNITE-1 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-13331) Document .NET thin client features implemented in 2.9 release

Aleksey Plekhanov created IGNITE-13331: -- Summary: Document .NET thin client features implemented in 2.9 release Key: IGNITE-13331 URL: https://issues.apache.org/jira/browse/IGNITE-13331 Project:

Ignite-core/TcpDiscoverySPI: Vyacheslav Koptilin , Vladimir Steshin. PR updated according to your recommendations. new questions.

Vladimir thank you for reviewing my PR However I still have some questions. I've updated the source code according to your recommendations. TcpDiscoveryConnectionCheckMessage message stub is used according to your comment *// Replace logic routine message with a stub to update

[jira] [Created] (IGNITE-13332) Document .NET Native Near Cache

Aleksey Plekhanov created IGNITE-13332: -- Summary: Document .NET Native Near Cache Key: IGNITE-13332 URL: https://issues.apache.org/jira/browse/IGNITE-13332 Project: Ignite Issue Type:

[jira] [Created] (IGNITE-13334) Document initial tracing implementation

Aleksey Plekhanov created IGNITE-13334: -- Summary: Document initial tracing implementation Key: IGNITE-13334 URL: https://issues.apache.org/jira/browse/IGNITE-13334 Project: Ignite Issue

Re: Moving Ignite documentation to github

Artem, Ok, let's suggest edits for 2.9 release documentations via pull request to ignite-7595 branch if there are no other objections. чт, 6 авг. 2020 г. в 13:20, Artem Budnikov : > Alex, > > The documentation source files are still in the IGNITE-7595 branch. I > haven't pushed them to the

[jira] [Created] (IGNITE-13337) Performance drop in ignite-2.9 vs Ignite 2.8.1

Ivan Artukhov created IGNITE-13337: -- Summary: Performance drop in ignite-2.9 vs Ignite 2.8.1 Key: IGNITE-13337 URL: https://issues.apache.org/jira/browse/IGNITE-13337 Project: Ignite Issue

[jira] [Created] (IGNITE-13336) .NET: Misleading LINQ exception when expression can't be translated

Pavel Tupitsyn created IGNITE-13336: --- Summary: .NET: Misleading LINQ exception when expression can't be translated Key: IGNITE-13336 URL: https://issues.apache.org/jira/browse/IGNITE-13336 Project:

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

Hello, I've compared performances of 2.9 and 2.8.1 using Yardstick and some atomic/transactional/SQL operations. Ignite 2.9 is up to 7% slower in my configuration. Please see https://issues.apache.org/jira/browse/IGNITE-13337 for details. Is this performance drop a blocker for 2.9 release? --

Re: [DISCUSSION] Cache warmup

Hello, Alexey! Your comments are fair. 05.08.2020, 15:51, "Alexey Goncharuk" : > Kirill, > > Thank you for driving this discussion and implementation. > > A few points from my side: > * Agree that it will be best to keep the strategy interface private because > it will be very dependent on the

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

Hello! Alexey, I think that it is indeed related to IGNITE-13303 Can you check? Thanks, -- Ilya Kasnacheev ср, 5 авг. 2020 г. в 22:44, : > Hi Igniters, > > I've detected some new issue on TeamCity to be handled. You are more than >

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

Ivan, Thank you. We've got performance drop on our benchmarks too. We are trying to bisect changes and find problematic commit now. чт, 6 авг. 2020 г. в 14:51, Ivan Artiukhov : > Hello, > > I've compared performances of 2.9 and 2.8.1 using Yardstick and some > atomic/transactional/SQL

Re: Please grant me privileges to edit ignite wiki pages.

Hello! Do you have a Wiki account? What's its username? Thanks, -- Ilya Kasnacheev чт, 6 авг. 2020 г. в 11:01, Zhenya Stanilovsky : > > I`m currently working on cpp thin client transactions support [1] and need > to edit, for example this page [2]. > Can someone grant me this privileges ? >

Please grant me privileges to edit ignite wiki pages.

I`m currently working on cpp thin client transactions support [1] and need to edit, for example this page [2]. Can someone grant me this privileges ? thanks !   [1]  https://issues.apache.org/jira/browse/IGNITE-13308 [2] https://cwiki.apache.org/confluence/display/IGNITE/Thin+clients+features    

Re: Moving Ignite documentation to github

Denis, Artem, I've marked the "tracing" ticket as important. Also, I've added a new section to the release page [1] and created documentation tickets for some features. Now there is a documentation ticket exists for each important feature implemented in 2.9. I know that some Igniters are

[jira] [Created] (IGNITE-13335) Document changes to thin client binary protocol

Aleksey Plekhanov created IGNITE-13335: -- Summary: Document changes to thin client binary protocol Key: IGNITE-13335 URL: https://issues.apache.org/jira/browse/IGNITE-13335 Project: Ignite

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

I recently found, that control.sh is broken since 2.8.0 a little bit. Script returns always 0 code, despite the fact, that CommandHandler returns code correctly. Here is the issue https://issues.apache.org/jira/browse/IGNITE-13328, patch is available. пт, 31 июл. 2020 г. в 14:09, Alex Plehanov :

Re: Apache Ignite 3.0

Hello! I hope to see Apache Ignite release 3.0 as API trimming release. Let us correct external and internal APIs for which we have better ideas now, as well as remove old and deprecated code. We may also introduce new configuration mechanisms and user-facing API (such as cache-less native SQL

Re: Moving Ignite documentation to github

Alex, The documentation source files are still in the IGNITE-7595 branch. I haven't pushed them to the master yet, but I can do so if it is necessary. Or, you can add your changes to this branch. I added an instruction on how to contribute: