Re: IGNITE-13315, please review the pull request

Konstantin, thanks a lot for the contribution! I've reviewed and merged the improvement. Please do us a favor and: - In addition to the ticket number include its name in the email subject. Otherwise, most of the committers won't pay attention to the email and simply pass by. For

Re: IGNITE-12360 Migrate Storm module to ignite-extensions

Thank you Denis, I have merged the changes. We are very close to finishing up the modularization project. Regards, Saikat On Tue, Jul 28, 2020 at 2:08 PM Denis Magda wrote: > Thank you buddy for driving the modularization activity. The changes look > good to me. Feel free to merge the

IGNITE-13315, please review the pull request

Hello! Please review the changes. This PR contains one line:) Thanks. --- Kind Regards, Konstantin Sirotkin

Re: IGNITE-13069, please review pull request

Hello! Done, I divided the PR into five smaller ones 8090-8093,8095. Can someone please check the changes now? Thanks. --- Kind Regards, Konstantin Sirotkin > On 28 Jul 2020, at 22:18, Konstantin Sirotkin > wrote: > > Now I am working on breaking this PR into smaller parts. > > On

Re: IGNITE-12781 - ache_put event contains the node id instead of the remote_client subject id

Hello! If this issue blocks you, I suggest investing time in fixing it, providing a patch perhaps? Regards, -- Ilya Kasnacheev вс, 26 июл. 2020 г. в 12:46, VeenaMithare : > Posting this here, as guided in the ignite users group. > Hi Team, > > 1. I noticed that this issue ( >

Re: Share my Apache Ignite Use Case

Hello! If you expected to attach or link to some document, it isn't there. Regards, -- Ilya Kasnacheev пт, 24 июл. 2020 г. в 14:02, : > Kindly share Apache Ignite Use Case with respect to all acpect. > > > > > > > Best Regards, > Sonali Dive > Strategy & Architecture - Centre of Excellence

Add IgniteInvalidGridStateException instead of IllegalStateException in KernalGateway

Dear Igniters, I'm working on a bug in .NET code that handles transaction states (jira ticket ). And I need a way to handle stopped grid exception, so I think it will make sense to throw a specialized exception type in this case instead of a

Re: please advise. I'm not sure why TeamCity build fails

Hi Aleksey! Apache Ignite is pretty complex thing with huge amount of different tests in several languages. So some of them will fail time to time and it considered normal (at least right now). To verify your PR you could take an advantage of Apache Ignite Teamcity Bot [1]. It will check

[Apache Ignite Virtual Meetup] Building a Blockchain Network with Apache Ignite

Hi Igniters! Recently, we started Virtual Meetup[1]. One of our goals is to create a space where app developers can share their experience of using Ignite. So, I’m happy to invite you to a talk by Branimir Angelov on August 11[2]. Branimir will introduce a stream-based, horizontally scalable

please advise. I'm not sure why TeamCity build fails

Hi guys Please help me to understand the TeamCity test failing problem. I created a pull request and TeanCity failed. As part of the problem investigation I've created a new pull request with minor code change to check how TeamCity would test this minor change. I've just added a comment line.

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

Ivan, IGNITE-13306 cherry-picked to 2.9 пт, 31 июл. 2020 г. в 13:43, Ivan Rakov : > Hi Alex, > > https://issues.apache.org/jira/browse/IGNITE-13306 is merged to master. > Can you please cherry-pick to 2.9? > > On Thu, Jul 30, 2020 at 7:42 PM Ilya Kasnacheev > wrote: > >> Hello! >> >> I don't

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

Hi Alex, https://issues.apache.org/jira/browse/IGNITE-13306 is merged to master. Can you please cherry-pick to 2.9? On Thu, Jul 30, 2020 at 7:42 PM Ilya Kasnacheev wrote: > Hello! > > I don't think that IGNITE-13006 > is a blocker in any >

Real-Time TeamCity Test Reporting

Hello! I have merged https://issues.apache.org/jira/browse/IGNITE-12934 This means that tests will now be reported to TeamCity as they go, instead of being registered only when the suite is complete (and discarded if the suite fails). I have also improved handling of `assertion violated' tests.

Re: [DISCUSS] Best way to re-encrypt existing data (TDE cache key rotation).

Hello, I'll expand the answer a bit about calculating CRC, the problem is not that it is calculated twice, but that now for encrypted pages, EncryptedFileIO checks physical integrity, and FilePageStore checks the correctness of the encryption key, but from my point of view, it should be vice

Re: [DISCUSS] Best way to re-encrypt existing data (TDE cache key rotation).

Hello, > 10. Question - CRC is read in two places encryptionFileIO and > filePageStore - what should we do with this? We need to calculate the CRC of encrypted data, because we may be using the wrong encryption key to decrypt data, in which case we will not understand if the physical integrity