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

Thanks Ivan and Denis for clarifying things. I think we are in good shape :) Thanks, Raymond On Tue, Jun 30, 2020 at 10:29 AM Denis Magda wrote: > Hi Raymond, > > You will not come across any internode-communication issues with your > deployment configuration as long as the servers and

[DISCUSSION] Tracing: IGNITE-13060

Hello Igniters, I'd like to discuss with you and then donate changes related to IGNITE-13060 In very brief it's an initial tracing implementation that allows to thrace Communication, Exchange, Discovery and Transactions. Spi concept is used

[jira] [Created] (IGNITE-13197) Add ImportOrder rule to checkstyle

Nikolay Izhikov created IGNITE-13197: Summary: Add ImportOrder rule to checkstyle Key: IGNITE-13197 URL: https://issues.apache.org/jira/browse/IGNITE-13197 Project: Ignite Issue Type:

Re: [DISCUSSION] Ignite integration testing framework.

Folks, First, I've created PR [1] with ducktests improvements PR contains the following changes - Pme-free switch proof-benchmark (2.7.6 vs master) - Ability to check (compare with) previous releases (eg. 2.7.6 & 2.8) - Global refactoring -- benchmarks javacode simplification -- services python

IEP-50 Thin Client Continuous Queries

Igniters, Let's discuss Thin Client Continuous Queries, I've prepared an IEP [1] and a PoC [2]. [1] https://cwiki.apache.org/confluence/display/IGNITE/IEP-50%3A+Thin+Client+Continuous+Queries [2] https://github.com/apache/ignite/pull/7966

Partitioned mode issue

I have this scenario: 1 Cluster with 2 server nodes and 1 cache configured with partitioned mode. Also 1 client node for consuming the data. With this settings, if I try to recover all the data with the client node I lose some information, for example if I have A, B, C and D data I recover only

Re: [CODESTYLE] Import order

Hello Nikolay, Can we put those IDEA settings to git, so everyone has them automatically? I know Rider has this feature for C# code (team-shared settings), surely IDEA has it too? On Tue, Jun 30, 2020 at 5:39 PM Nikolay Izhikov wrote: > Hello, Igniters. > > For now, we don’t have checkstyle

[CODESTYLE] Import order

Hello, Igniters. For now, we don’t have checkstyle rule to force import order codestyle [1] Therefore there is many violations of this rule in current codebase. Moreover, during review, I saw many not related changes regarding import reorder. I’ve prepared a PR to fix this [2] It contains:

Re: [DISCUSSION] Ignite.C++ and CMake

Ok, CMake now is the only option to build C++ on non-windows platforms. Autotools is removed from master. Many thanks to Igor Sapego, Zhenya Stanilovsky, Nickolay Izhikov and Ilya Kasnacheev for review, testing and suggestions. вт, 23 июн. 2020 г. в 18:42, Ivan Daschinsky : > I suppose, that

Re: [DISCUSSION] Ignite.C++ and CMake

This is awesome, thanks everyone! I've tried following the instructions, and the following two steps seem to be misleading: * mkdir cmake-build-[release|debug] * cd ./cmake-build-[release|debug] When I run cmake in the newly created cmake-build-debug dir, I get: CMake Error: The source directory

Re: [CODESTYLE] Import order

Hello, Pavel. > Can we put those IDEA settings to git Yes we can. Ignite_codeStyle.xml updated to follow correct import order. > 30 июня 2020 г., в 18:11, Pavel Tupitsyn написал(а): > > Hello Nikolay, > > Can we put those IDEA settings to git, so everyone has them automatically? > I know

Re: Partitioned mode issue

Hi Toni, With partitioned caches, a node keeps a subset of your data. You need to have at least one backup copy configured. Refer to this resource that explains the partitioning with clarity: https://www.gridgain.com/docs/latest/developers-guide/data-modeling/data-partitioning - Denis On Tue,

Re: Website link update

Hi community, The current site of the Chinese version of the document is https://liyuj.gitee.io , this site will stop maintenance in the future. The new site is located at https://www.ignite-service.cn/doc/java, is there anyone in the community can help with the change in

Re: [DISCUSSION] Ignite.C++ and CMake

Pavel, pay attention to two dots at the end. All build files should stay at current dir, and cmake-build-release is supposed to be a build root. And this directory is added to gitignore. Actually, build directory can be everywhere, but you should pass path to dir, that contains root

Re: Website link update

Hi, I've updated the documentation URL. Thanks a lot for maintaining the Chinese version throughout the years. Hope local application developers appreciate your efforts! - Denis On Tue, Jun 30, 2020 at 5:03 PM 18624049226 <18624049...@163.com> wrote: > Hi community, > > The current site of

Ignite thin client in Rust

Igniters, I've been learning the Rust language lately and though that creating a thin client in Rust would be a great exercise. I went ahead and create a prototype which currently supports only put and get operations with primitives and strings: https://github.com/vkulichenko/ignite-rust-client

Re: [DISCUSSION] Ignite.C++ and CMake

Let me explain with details. CMake is unusual from other build systems, that it can separate build root and source root. Moreover, it is strongly discouraged to mix them. Benefits: 1. You can have many build with different options using same source. 2. You can build project with different