Re: [DISCUSSION] Framework for SQL performance regressions detection.

Roman, Probably you are right that the SQL benchmarks need to be incorporated into the existing 'ignite-benchmarks' module. Please disregard my suggestion of setting a dedicated repository. - Denis On Sat, May 23, 2020 at 6:12 AM Roman Kondakov wrote: > Hi Denis, > > I'm not sure we need a

Re: [DISCUSS] Extra test coverage for ACTIVE_READ_ONLY cluster state

Maxim, I've created a ticket [1] for this change. [1] https://issues.apache.org/jira/browse/IGNITE-13079 вт, 26 мая 2020 г. в 20:09, Sergey Antonov : > Maxim, I'd prefer to do this with a separate ticket. > > вт, 26 мая 2020 г. в 19:59, Maxim Muzafarov : > >> Sergey, >> >> Sounds good! >>

Re: Re[2]: [VOTE] Release Apache Ignite 2.8.1 RC1

+1 (binding) Download binary, run some examples. Checked zookeeper dependencies. On Tue, 26 May 2020 at 12:02, Zhenya Stanilovsky wrote: > > > Nikolay, performance boost is always good news for all customers at all and > for me too ) > Can you give more info (looks like in different mail

[jira] [Created] (IGNITE-13079) Replace deprecated cluster activation methods in tests.

Sergey Antonov created IGNITE-13079: --- Summary: Replace deprecated cluster activation methods in tests. Key: IGNITE-13079 URL: https://issues.apache.org/jira/browse/IGNITE-13079 Project: Ignite

Re: [DISCUSS] Extra test coverage for ACTIVE_READ_ONLY cluster state

Maxim, I'd prefer to do this with a separate ticket. вт, 26 мая 2020 г. в 19:59, Maxim Muzafarov : > Sergey, > > Sounds good! > Should we consider removing the deprecated methods `active()`, > `active(boolean active)` from tests also? > > On Tue, 26 May 2020 at 12:18, Sergey Antonov > wrote: >

Re: [DISCUSS] Extra test coverage for ACTIVE_READ_ONLY cluster state

Sergey, Sounds good! Should we consider removing the deprecated methods `active()`, `active(boolean active)` from tests also? On Tue, 26 May 2020 at 12:18, Sergey Antonov wrote: > > Hello, Igniters. > > I introduced cluster read-only mode [1] and a new API for cluster state > change [2]. At the

Re[4]: Proposal: set default transaction timeout to 5 minutes

Of course, i just thinking about huge persistent installation and guys who not  carefully reads Release Notes ) In case of long tx timeouts by design, they can easily fix default timeout with just one jmx call.    >Zhenya, > >Can you please elaborate? >Why we need to change default TX timeout

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

Stephen, looks great! I do mostly the same things in C++ code. Thank you! вт, 26 мая 2020 г. в 18:33, Stephen Darlington < stephen.darling...@gridgain.com>: > Not sure if it’ll help, but I made some changes to get it working on a Mac > with the current built system. There may be some code worth

Re: Re[2]: Proposal: set default transaction timeout to 5 minutes

Zhenya, Can you please elaborate? Why we need to change default TX timeout via JMX? It looks feasible and perhaps may work as a hotfix for live deployments experiencing issues with long transactions, but it's definitely a separate issue. On Fri, May 22, 2020 at 6:20 PM Zhenya Stanilovsky wrote:

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

Not sure if it’ll help, but I made some changes to get it working on a Mac with the current built system. There may be some code worth taking. https://github.com/apache/ignite/pull/4872 Regards, Stephen > On 26 May 2020, at 16:02, Ivan Daschinsky

[jira] [Created] (IGNITE-13078) С++: Add CMake build support

Ivan Daschinskiy created IGNITE-13078: - Summary: С++: Add CMake build support Key: IGNITE-13078 URL: https://issues.apache.org/jira/browse/IGNITE-13078 Project: Ignite Issue Type:

Re: IGNITE-12359 Migrate RocketMQ module to ignite-extensions

Hello! We still have a mention of it in assembly/libs/README.txt - I think we should remove it alongside with some others. I'm not sure where this file goes to. Otherwise, LGTM. Regards, -- Ilya Kasnacheev пн, 25 мая 2020 г. в 20:13, Saikat Maitra : > Hi Ilya, > > Thank you for reviewing

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

I appreciate any help, thank you, Ilya. Currently I have a small PR without ticket (link in first post),but I decided not to file a jira issue before discussion. Now I see, that this feature are of great interest to community. So I file a ticket, test myself on my home laptop (ubuntu 20.04) and

Re: [jira] [Created] (IGNITE-13065) Ignite Web Console 2.7.0 not working when scanning cache Error: Cannot read property 'length' of null

I have the same issue. Can anybody help with this? -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[DISCUSSION] IEP-47 Native persistence defragmentation

Hello Igniters, I'd like to discuss this new IEP with you: [1]. The main idea is to have a procedure that relocates pages to the top of the file as compact as possible which allows us to trim the file and increase its fill-factor. It will be configured manually and executed after the restart, but

Re: Prevent insertion of cache entry if the binary field type and the type of the query entity do not match.

Hello! I'm not aware about any mechanism like this one built in Apache Ignite. I advise you to wrap Ignite's APIs into ones of your own and avoid using raw Ignite API. This way you will make sure to do these checks on your own. Regards, -- Ilya Kasnacheev пн, 25 мая 2020 г. в 15:22, Pavel

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

Hello! I will assist with checking on Linux if you would contribute a patch. Please start with a ticket (or even an IEP maybe?) Regards, -- Ilya Kasnacheev вт, 26 мая 2020 г. в 16:47, Ivan Daschinsky : > Guys, I will certainly thoroughly test my fix not only unices, but on > windows too. >

[jira] [Created] (IGNITE-13077) .NET transaction gets overwritten for multiple Ignite trying to start transactions in one thread

Sergey Stronchinskiy created IGNITE-13077: - Summary: .NET transaction gets overwritten for multiple Ignite trying to start transactions in one thread Key: IGNITE-13077 URL:

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

Guys, I will certainly thoroughly test my fix not only unices, but on windows too. And I will describe it very thoroughly. When I was C++ developer (more than 10 years ago), I have not any trouble at all with CMake and Visual Studio 2005. Everything works and works good. Moreover, you can build

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

Hello, Igor. > Nikolay, removing support for a certain build system is a breaking change. No, it’s not. Why do you think so? Development environment and build system is a subject to change in any project. We can drop or add support of any build system any time we want. > 26 мая 2020 г., в

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

Hello! I don't see why we can't get rid of autotools in a minor release, provided that cmake actually works. Removing native VS support may be a different thing. Build system and precise set of dependencies is not a part of public API in my opinion. Regards, -- Ilya Kasnacheev вт, 26 мая

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

Igor, I just said about native support from Visual Studio, not from cmake itself. Modern cmake can generate projects even for Visual Studio 2008 [1] [1] -- https://cmake.org/cmake/help/v3.16/generator/Visual%20Studio%209%202008.html вт, 26 мая 2020 г. в 16:16, Igor Sapego : > Nikolay, removing

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

Nikolay, removing support for a certain build system is a breaking change. Ivan, in C++ world there are companies that still use VS 2012 or even 2010. Best Regards, Igor On Tue, May 26, 2020 at 4:08 PM Ivan Daschinskiy wrote: > Guys, thank you all for support > > >> The only concern I have

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

Hello, Igor. I’m ++1 for this change. How build system relates to major version of product? I think we can change the way we build modules any time we want. > 26 мая 2020 г., в 16:02, Igor Sapego написал(а): > > Great! > > Let's start with creating a TC suite for it. > > The only concern I

[jira] [Created] (IGNITE-13076) Cluster read-only mode doesn't affect LOCAL caches

Sergey Antonov created IGNITE-13076: --- Summary: Cluster read-only mode doesn't affect LOCAL caches Key: IGNITE-13076 URL: https://issues.apache.org/jira/browse/IGNITE-13076 Project: Ignite

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

Great! Let's start with creating a TC suite for it. The only concern I have is that it is one more build system to support. Should we get rid of autotools in 3.0? Best Regards, Igor On Tue, May 26, 2020 at 2:44 PM Alexey Kukushkin wrote: > +1. I recently completed a cross-IDE (MS Visual

[jira] [Created] (IGNITE-13075) NPE on request JDBC metadata

Konstantin Orlov created IGNITE-13075: - Summary: NPE on request JDBC metadata Key: IGNITE-13075 URL: https://issues.apache.org/jira/browse/IGNITE-13075 Project: Ignite Issue Type: Bug

Re: Extended logging for rebalance performance analysis

Hi, Kirill. 2. Ok for me. 3. We already have log message about rebalance cancellation for specific rebalanceId and log message about new rebalancing has started with next rebalanceId. 5. We already have summary information per group for each supplier added in p.2 I would avoid duplication here

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

+1. I recently completed a cross-IDE (MS Visual Studio & GCC/GDB) Ignite C++ project and CMake in Ignite C++ would save me a day of effort. вт, 26 мая 2020 г. в 12:09, Pavel Tupitsyn : > +1 > > On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky > wrote: > > > > > Ivan huge +1 with your

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

> Nikolay, btw, what's your thinking on the approach proposed by me? Makes sense. > 26 мая 2020 г., в 14:07, Alexey Sasov написал(а): > > Hello. Looks good. What whould be returned from the query like this "select > _key from cache" if we don't know the type of the key? ExpandoObject, Tuple, >

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

Hello. Looks good. What whould be returned from the query like this "select _key from cache" if we don't know the type of the key? ExpandoObject, Tuple, BinaryObject? How would you change ICache interface which has this member? /// Queries cache. /// Query. /// Cursor.

[jira] [Created] (IGNITE-13074) Thin client: Default compute cluster group should be "server nodes", but currently "all nodes"

Aleksey Plekhanov created IGNITE-13074: -- Summary: Thin client: Default compute cluster group should be "server nodes", but currently "all nodes" Key: IGNITE-13074 URL:

Re: [jira] [Created] (IGNITE-13065) Ignite Web Console 2.7.0 not working when scanning cache Error: Cannot read property 'length' of null

Folks, Indeed it seems that there is no web-console docker image for 2.8.0. Can someone help here? Who knows what should be done to deploy new image? 2020-05-22 18:43 GMT+03:00, david (Jira) : > david created IGNITE-13065: > -- > > Summary: Ignite Web

[jira] [Created] (IGNITE-13073) NPE on closing node in communication SPI

Nikita Tolstunov created IGNITE-13073: - Summary: NPE on closing node in communication SPI Key: IGNITE-13073 URL: https://issues.apache.org/jira/browse/IGNITE-13073 Project: Ignite Issue

Re: [DISCUSS] TC bot instructions for open source contributors

Hi Ivan, Igniters, Yeah, our HTC is kind of a mile long. One try I've done to get a shorter version is GitHub's Contributing.MD https://github.com/apache/ignite/blob/master/CONTRIBUTING.md#contributing-to-apache-ignite I used to share both versions - short and long to new contributors. But I

[jira] [Created] (IGNITE-13072) Synchronization problems when different classloaders are used for deployment of same class

Vladislav Pyatkov created IGNITE-13072: -- Summary: Synchronization problems when different classloaders are used for deployment of same class Key: IGNITE-13072 URL:

[DISCUSS] Extra test coverage for ACTIVE_READ_ONLY cluster state

Hello, Igniters. I introduced cluster read-only mode [1] and a new API for cluster state change [2]. At the moment we don't have good test coverage for this feature. I'm going to fix it and write tests and check that operations are *denied *in read-only mode: - data structures usage -

[jira] [Created] (IGNITE-13071) Improve test coverage for read-only cluster state

Sergey Antonov created IGNITE-13071: --- Summary: Improve test coverage for read-only cluster state Key: IGNITE-13071 URL: https://issues.apache.org/jira/browse/IGNITE-13071 Project: Ignite

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

+1 On Tue, May 26, 2020 at 12:02 PM Zhenya Stanilovsky wrote: > > Ivan huge +1 with your proposal. > I had some problems with odbc tests building too, looks like cmake will > make it more easy. > >Hello Igniters. > > > >I’d like to discuss porting build process of Ignite.C++. I think that >

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

Ivan huge +1 with your proposal. I had some problems with odbc tests building too, looks like cmake will make it more easy. >Hello Igniters. > >I’d like to discuss porting build process of Ignite.C++. I think that there is >time to change it. > >*Motivation* >Currently, it is hard to build

Re[2]: [VOTE] Release Apache Ignite 2.8.1 RC1

Nikolay, performance boost is always good news for all customers at all and for me too ) Can you give more info (looks like in different mail thread) ? What kind of benchmarks have been done, is it about persistence or both ? thanks ! >+1 (binding). > >We made some internal benchmarking and

Re: [VOTE] Release Apache Ignite 2.8.1 RC1

+1 (binding). We made some internal benchmarking and found performance boost in comparison with 2.8.0 > 22 мая 2020 г., в 22:42, Denis Magda написал(а): > > + 1 (binding) > > Downloaded a binary version, started a cluster and ran some samples. > > - > Denis > > > On Fri, May 22, 2020 at

[DISCUSSION] Ignite.C++ and CMake

Hello Igniters. I’d like to discuss porting build process of Ignite.C++. I think that there is time to change it. *Motivation* Currently, it is hard to build Ignite.C++. Different build process for windows and linux, lack of building support on Mac OS X (quite popular OS among developers),