Re: IGNITE-12952 Enable travis ci for ignite-extensions

Hi Maxim, Pavel Can you please share more info about how travis build was enabled for ignite repo? I tried to execute the travis CI build for ignite-extensions but I do not have sufficient access to enable the travis build for ignite-extensions repo. Regards, Saikat On Sun, May 31, 2020 at

Re: Tool for performance statistics reports

Hello Nikita, I observed we have an open PR in ignite repo for this feature with different set of changes compared to ignite extensions repo. apache/ignite#7693 https://github.com/apache/ignite-extensions/pull/16 Can you please share more info on

Re: [DISCUSS] Fix confusing "Used by" on GitHub

I can see the badge being signed in. In fact, there are many more dependents on our modules and packages: https://github.com/apache/ignite/network/dependents The badge displays "apache-ignite-client" stats by default because the package goes

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

Ivan, Sergey, How much effort should we put to resolve the issue with continuous queries? Are you working on that issue actively? Let's try to guess what would be the ETA. - Denis On Wed, Jun 10, 2020 at 3:55 AM Ivan Bessonov wrote: > Hello, > > Sorry for the delay. Sergey Chugunov

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

Sergey, Thanks for the detailed explanation and for covering all corner cases. Considering the improvement's criticality, I would continue moving in the initial direction and add that particular configuration property. Potentially, we can put more effort throughout an Ignite 3.0 timeframe and

Re: [DISCUSS] Add flag methods to ClusterState enum

Pavel, Alexei thank you for your replays. > is this one special in some way? Yes. We have two "active" cluster states: ACTIVE, ACTIVE_READ_ONLY. Probably, I chose the wrong method's name, but I mean that in "active" state the caches must be started. > But it looks like we do not need methods

Re: [DISCUSS] Fix confusing "Used by" on GitHub

A screenshot from my browser [1]. I suppose we still think about proper repository URLs. P.S. I do not see "Used by" when I am not logged in. Might it be the case? [1]

Re: [DISCUSS] Fix confusing "Used by" on GitHub

Hello! Still nothng. Maybe they are A/B testing this feature? In this case, I suggest we wait. Regards, -- Ilya Kasnacheev ср, 10 июн. 2020 г. в 22:40, Pavel Tupitsyn : > Ilya, Andrey, try a forced reload of the page: > [image: image.png] > > > On Wed, Jun 10, 2020 at 10:30 PM Andrey Gura

[MTCGA]: new failures in builds [5376278] 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: [DISCUSS] Fix confusing "Used by" on GitHub

Ilya, Andrey, try a forced reload of the page: [image: image.png] On Wed, Jun 10, 2020 at 10:30 PM Andrey Gura wrote: > +1 > > I don't see any badges. > > On Wed, Jun 10, 2020 at 10:27 PM Ilya Kasnacheev > wrote: > > > > Hello! > > > > I don't see such a badge. Instead I see "Watch" "Star"

Re: [DISCUSS] Fix confusing "Used by" on GitHub

+1 I don't see any badges. On Wed, Jun 10, 2020 at 10:27 PM Ilya Kasnacheev wrote: > > Hello! > > I don't see such a badge. Instead I see "Watch" "Star" "Fork". > > Regards, > -- > Ilya Kasnacheev > > > ср, 10 июн. 2020 г. в 20:58, Ivan Pavlukhin : > > > Hi Igniters, > > > > I noticed that we

Re: [DISCUSS] Fix confusing "Used by" on GitHub

Hello! I don't see such a badge. Instead I see "Watch" "Star" "Fork". Regards, -- Ilya Kasnacheev ср, 10 июн. 2020 г. в 20:58, Ivan Pavlukhin : > Hi Igniters, > > I noticed that we have a confusing "Used by" badge on a GitHub mirror > repository main page [1] (the badge is located in a line

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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New test failure in master CacheSerializableTransactionsTest.testNoOptimisticExceptionOnChangingTopology

Re: [DISCUSS] Add flag methods to ClusterState enum

But it looks like we do not need methods *readOnly *and *inactive*. What is the point in adding them ? ср, 10 июн. 2020 г. в 21:05, Alexei Scherbakov : > Sergey Antonov, > > The proposal looks good to me. > Use of org.apache.ignite.cluster.ClusterState#active adds a > boilerplate code (a lot of

Re: [DISCUSS] Add flag methods to ClusterState enum

Sergey Antonov, The proposal looks good to me. Use of org.apache.ignite.cluster.ClusterState#active adds a boilerplate code (a lot of static imports) and does an unnecessary state check. ср, 10 июн. 2020 г. в 19:02, Pavel Tupitsyn : > Sergey, > > I disagree - looks weird. > We have lots of

[DISCUSS] Fix confusing "Used by" on GitHub

Hi Igniters, I noticed that we have a confusing "Used by" badge on a GitHub mirror repository main page [1] (the badge is located in a line with Star and Fork badges). It reports only a couple of usages while there are much more. Actually it shows only apache-ignite-client NPM package usages. As

Re: [DISCUSS] Add flag methods to ClusterState enum

Sergey, I disagree - looks weird. We have lots of enums, is this one special in some way? Thanks, Pavel On Wed, Jun 10, 2020 at 6:58 PM Sergey Antonov wrote: > Igniters, I'd like to propose a small improvement in ClusterState class. I > want to remove the static method boolean

[DISCUSS] Add flag methods to ClusterState enum

Igniters, I'd like to propose a small improvement in ClusterState class. I want to remove the static method boolean ClusterState#active and add methods to the enum: - boolean active() - boolean readOnly() - boolean inactive() >From my point of view these methods more useful than

Re: request for contributors permissions

Hello! I can see that you are already added to contributors. You should be able to assign issues to yourself. Regards, -- Ilya Kasnacheev ср, 10 июн. 2020 г. в 18:06, Aleksey Kurinov : > Hello > > i've registered on https://issues.apache.org/jira/secure/Dashboard.jsp and > according to >

[jira] [Created] (IGNITE-13144) Add attribute methods to ClusterState enum

Sergey Antonov created IGNITE-13144: --- Summary: Add attribute methods to ClusterState enum Key: IGNITE-13144 URL: https://issues.apache.org/jira/browse/IGNITE-13144 Project: Ignite Issue

request for contributors permissions

Hello i've registered on https://issues.apache.org/jira/secure/Dashboard.jsp and according to https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute I'm requesting contributors permissions thank you Aleksei Kurinov

[jira] [Created] (IGNITE-13143) Persistent store defragmentation

Sergey Chugunov created IGNITE-13143: Summary: Persistent store defragmentation Key: IGNITE-13143 URL: https://issues.apache.org/jira/browse/IGNITE-13143 Project: Ignite Issue Type: New

[jira] [Created] (IGNITE-13142) SQL constraint not null added on key prevents correct inserts

Sergey Kalashnikov created IGNITE-13142: --- Summary: SQL constraint not null added on key prevents correct inserts Key: IGNITE-13142 URL: https://issues.apache.org/jira/browse/IGNITE-13142

[jira] [Created] (IGNITE-13141) Modify .NET counterpart of IgniteCluster to include functionality of Cluster ID and tag

Sergey Chugunov created IGNITE-13141: Summary: Modify .NET counterpart of IgniteCluster to include functionality of Cluster ID and tag Key: IGNITE-13141 URL: https://issues.apache.org/jira/browse/IGNITE-13141

Re: Not able to connect multiple slaves to Master

Hello! I'm not really sure what do you mean by 'starting master on one server'. Do you mean a server node? And you can only get a single client to connect to it? Can you provide logs from clients and servers? Regards, -- Ilya Kasnacheev вт, 9 июн. 2020 г. в 21:33, imran kazi : > Hi Team, >

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

> Is that OK? We shouldn’t add any code that is broke some existing, widely used feature. Let’s fix it before the merge. > 10 июня 2020 г., в 13:54, Ivan Bessonov написал(а): > > Hello, > > Sorry for the delay. Sergey Chugunov (sergey.chugu...@gmail.com) just > replied > to the main

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

Hello, Sorry for the delay. Sergey Chugunov (sergey.chugu...@gmail.com) just replied to the main conversation about "communication via discovery" [1]. We work on it together and recently have found one hard-to-fix scenario, detailed description is provided in Sergey's reply. In short, July 10th

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

Denis, Val, Idea of prohibiting servers to open connections to clients and force clients to always open "inverse connections" to servers looks promising. To be clear, by "inverse connections" I mean here that server needed to communicate with client requests client to open a connection back

Re: IGNITE-12808 Allow create tables for existing caches

I will take a look. > 8 июня 2020 г., в 15:17, Ivan Daschinsky написал(а): > > Hi Igniters. > > I've recently submitted patch[1] that implemented subj. > Any help with review would be appreciated. > > > [1] - https://issues.apache.org/jira/browse/IGNITE-12808 > -- > Sincerely yours, Ivan