Request for contributors permissions

Hello, as discussed in this thread I would like to contribute to IGNITE-6499. Would you mind giving me the right to contribute. Thanks in advance -- Sent from:

[DISCUSSION] Ignite integration testing framework.

Hello, Igniters. I created a PoC [1] for the integration tests of Ignite. Let me briefly explain the gap I want to cover: 1. For now, we don’t have a solution for automated testing of Ignite on «real cluster». By «real cluster» I mean cluster «like a production»: * client and server

Re: Request for contributors permissions

Hello Steve, I added your JIRA account to a contributors list. Now you can assign tickets to yourself. Looking forward for your contributions! 2020-05-21 9:52 GMT+03:00, steve.hostett...@gmail.com : > Hello, > > as discussed in this thread >

Re[2]: [DISCUSS] Ignite process exit code on node stop by failure handler

Thank you Sergey, as for me — very useful proposal huge +1 here.   >Четверг, 21 мая 2020, 0:51 +03:00 от Sergey Antonov >: >  >I've created the Ignite ticket for this improvement [1]. > >[1] https://issues.apache.org/jira/browse/IGNITE-13047 > >чт, 21 мая 2020 г. в 00:46, Sergey Antonov <

Re: [DISCUSSION] Ignite integration testing framework.

Hello, Anton. > Could you please explain how to perform testing on the different environments? Different JDK: 1. We should prepare our environment and put the desired JDK in the known locations. [/opt/jdk1.8, /opt/jdk11], for example. 2. We should parametrize test and just setup java

Re: [DISCUSSION] Ignite integration testing framework.

Nikolay, Great proposal! Could you please explain how to perform testing on the different environments? For Example, you provided a rebalance test. Is it possible to perform this test with TDE enabled? Is it possible to perform it on custom OS (eg. Windows)? Is it possible to perform in on bare

[jira] [Created] (IGNITE-13049) AssertionError with JmxExporterSpi on cache stop. Test testCacheConfigSingleLineOutputFormatTwoNodeManyCaches

Maxim Muzafarov created IGNITE-13049: Summary: AssertionError with JmxExporterSpi on cache stop. Test testCacheConfigSingleLineOutputFormatTwoNodeManyCaches Key: IGNITE-13049 URL:

[jira] [Created] (IGNITE-13048) WAL FSYNC mode doesn't work with disabled archiver

Ivan Bessonov created IGNITE-13048: -- Summary: WAL FSYNC mode doesn't work with disabled archiver Key: IGNITE-13048 URL: https://issues.apache.org/jira/browse/IGNITE-13048 Project: Ignite

Re: [DISCUSSION] Separate code sanity check and build task

Hi Ivan, Thanks for your reply! It’s better to get an answer late than never :) -- Regards, Konstantin Orlov > On 18 May 2020, at 09:04, Ivan Pavlukhin wrote: > > Hi Konstantin, > > Surprisingly, I found your message in a Spam folder (gmail). > > We had discussions about the subject

[jira] [Created] (IGNITE-13050) ClusterGroup that is recomputed on topology change

Ivan Bessonov created IGNITE-13050: -- Summary: ClusterGroup that is recomputed on topology change Key: IGNITE-13050 URL: https://issues.apache.org/jira/browse/IGNITE-13050 Project: Ignite

[jira] [Created] (IGNITE-13057) Do not print /tmp path if pds file is not stored in tmp folder.

Semyon Danilov created IGNITE-13057: --- Summary: Do not print /tmp path if pds file is not stored in tmp folder. Key: IGNITE-13057 URL: https://issues.apache.org/jira/browse/IGNITE-13057 Project:

Re: [DISCUSSION] New Ignite settings for IGNITE-12438 and IGNITE-13013

Ivan, Have you considered eliminating server to client connections altogether? Or, at the very least making the "client to server only" mode the default one? All the suggested names are confusing and not intuitive, and I doubt we will be able to find a good one. A server initiating a TCP

Re: Using GraalVM instead of standard JVM

Folks, I've looked into GraalVM and would like to share some observations and suggestions: 1. GridGain nodes running on Graal can execute native Node.JS, Python, LLVM (C/C++) code. This feature will let Ignite developers who are not using Java as their primary programming language, deploy their

Re: Request for contributors permissions

Thanks a lot -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

Denis,I like your idea. It would be like native "OKVM" (Object-KeyValue Mapper) allowing Ignite to natively operate on domain entities. It also means no key and value data duplication and thus addressing the original SQL DML problem when only key field is modified.We could add a

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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to

Re: [DISCUSSION] New Ignite settings for IGNITE-12438 and IGNITE-13013

Ivan, Considering that the setting controls the way a communication SPI connection is open I would add the new parameter to CommunicationSpi interface naming it as follows: > > CommunicationSpi.connectionInitiationMode > { > BIDIRECTIONAL, //both clients and servers initiate a connection >

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

> > I do acknowledge that this awkward usability issue is quite annoying and > complicates applications' architecture. Problem with Spring Data Sorry, sent the message with the first paragraph left unfinished. "Problem with Spring Data" - just wanted to highlight that the current separation on

Re: [DISCUSS] Apache Ignite mascot

Folks, thanks for sharing ideas. Let me find a designer who can turn the ideas into pictures. Then we can compare and adjust. - Denis On Sun, May 17, 2020 at 5:50 AM Manuel Núñez wrote: > What about a hellboy’s style animal?, with Ignite’s flame between the horns > > El 16 may 2020, a las

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

Folks, thanks for the details. I do acknowledge that this awkward usability issue is quite annoying and complicates applications' architecture. Problem with Spring Data At the moment, I use the workaround mentioned by Alexey Kukushkin. Guess many of us already use it in productions: -

[jira] [Created] (IGNITE-13054) Prevent nodes with stale data joining the active topology.

Alexey Scherbakov created IGNITE-13054: -- Summary: Prevent nodes with stale data joining the active topology. Key: IGNITE-13054 URL: https://issues.apache.org/jira/browse/IGNITE-13054 Project:

Re: [DISCUSSION] Ignite integration testing framework.

Hi Nikolay, Thanks for kicking off this conversation and sharing your findings with the results. That's the right initiative. I do agree that Ignite needs to have an integration testing framework with capabilities listed by you. As we discussed privately, I would only check if instead of

[jira] [Created] (IGNITE-13056) SchemaManager refactoring

Nikolay Izhikov created IGNITE-13056: Summary: SchemaManager refactoring Key: IGNITE-13056 URL: https://issues.apache.org/jira/browse/IGNITE-13056 Project: Ignite Issue Type: New Feature

Re: [DISCUSSION] Ignite integration testing framework.

Hello, Denis. There is no rush with these improvements. We can wait for Maxim proposal and compare two solutions :) > 21 мая 2020 г., в 22:24, Denis Magda написал(а): > > Hi Nikolay, > > Thanks for kicking off this conversation and sharing your findings with the > results. That's the right

Re: ExecutorServices hide assertions without logging and node stop

Folks, I've created an issue. https://issues.apache.org/jira/browse/IGNITE-13055 On Wed, 6 May 2020 at 10:28, Nikolay Izhikov wrote: > > Hello, Maxim. > > I can confirm this itching issue. > It also happens when some custom Security plugin throws an exception while > processing a communication

[jira] [Created] (IGNITE-13055) ExecutorServices must handle AssertionErrors and log uncaught exceptions

Maxim Muzafarov created IGNITE-13055: Summary: ExecutorServices must handle AssertionErrors and log uncaught exceptions Key: IGNITE-13055 URL: https://issues.apache.org/jira/browse/IGNITE-13055

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

Hello! Do you mind if I push additional change to fix English in some of these entries? A lot of these has times not concording with "fixed". Regards, -- Ilya Kasnacheev ср, 20 мая 2020 г. в 15:47, Nikolay Izhikov : > Hello, Igniters. > > I prepared a PR with release notes. > Please, take a

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

Hello! Please apply https://github.com/apache/ignite/pull/7832 Regards, -- Ilya Kasnacheev чт, 21 мая 2020 г. в 16:02, Nikolay Izhikov : > Hello, Ilya. > > Actually, I’m uploading RC0 right now. > Let’s include these fixes in RC1, if you don’t mind? > > > 21 мая 2020 г., в 16:00, Ilya

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

Hello, Ilya. Actually, I’m uploading RC0 right now. Let’s include these fixes in RC1, if you don’t mind? > 21 мая 2020 г., в 16:00, Ilya Kasnacheev > написал(а): > > Hello! > > Do you mind if I push additional change to fix English in some of these > entries? A lot of these has times not

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

Done, thanks. > 21 мая 2020 г., в 16:34, Ilya Kasnacheev > написал(а): > > Hello! > > Please apply https://github.com/apache/ignite/pull/7832 > > Regards, > -- > Ilya Kasnacheev > > > чт, 21 мая 2020 г. в 16:02, Nikolay Izhikov : > >> Hello, Ilya. >> >> Actually, I’m uploading RC0 right

[DISCUSSION] New Ignite settings for IGNITE-12438 and IGNITE-13013

Hello Igniters, I'd like to discuss with you changes related to [1] and [2]. Both issues are mostly the same so let's discuss the core idea. *Motivation.* There are certain environments that don't allow Ignite server nodes to open TCP connections to thick clients, e.g. K8S, AWS Lambda or Azure

[jira] [Created] (IGNITE-13053) resetLostPartitions is not working if invoked from a node where a cache not started

Alexey Scherbakov created IGNITE-13053: -- Summary: resetLostPartitions is not working if invoked from a node where a cache not started Key: IGNITE-13053 URL: https://issues.apache.org/jira/browse/IGNITE-13053

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

I vote for implementing this enhancement: having key information separated from value means either cluttering domain model with KeyValue/CacheEntry-like structures or developing an Ignite data access layer to insert key info into domain entity after getting it from Ignite. Although both the

[jira] [Created] (IGNITE-13051) Optimized affinity switch on baseline node left is broken for client topology

Alexey Scherbakov created IGNITE-13051: -- Summary: Optimized affinity switch on baseline node left is broken for client topology Key: IGNITE-13051 URL: https://issues.apache.org/jira/browse/IGNITE-13051

Re: [DISCUSSION] Key and Value fields with same name and SQL DML

Hello, Denis. This is the analogy of DB records. We've got keys in the table. But querying the record with the key we also have this key in the returned record. The question of having all data in the value is a domain driven one. If i have a model (ex. Person) containing PassportNo, I don't want

[jira] [Created] (IGNITE-13052) Calculate result of reserveHistoryForExchange in advance

Ivan Rakov created IGNITE-13052: --- Summary: Calculate result of reserveHistoryForExchange in advance Key: IGNITE-13052 URL: https://issues.apache.org/jira/browse/IGNITE-13052 Project: Ignite