[MTCGA]: new failures in builds [4627134] 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: nodes are restarting when i try to drop a table created with persistence enabled

Shiva, Does this issue still exist? Ignite Dev how do we debug this sort of thing? - Denis On Tue, Sep 17, 2019 at 7:22 AM Shiva Kumar wrote: > Hi dmagda, > > I am trying to drop the table which has around 10 million records and I am > seeing "*Out of memory in data region*" error messages

Re: Please grant jira-user privilege to me.

Ken, As responded in Slack, you should be able to change the ticket status as long as you're in the contributors' list. - Denis On Tue, Sep 24, 2019 at 7:45 AM Ken Cheng wrote: > Hi dev, > > Right now I am working on > > https://issues.apache.org/jira/browse/IGNITE-11008 >

Re: Spark examples on TC

Nikolay, Thanks for the details. How about enforcing JDK 8 for the Spark integration in general and run its tests on the VM only? We'll do this until Spark community fully support JDK 11+. As for Spark 2.4.0 module [1], how about releasing Ignite 2.7.7 with Spark related changes only? As long as

Re: Improvements for P2P class loading

Denis, Why do we broadcast the request to all the nodes in case of scenario a)? There should be a reason for that. Alex Goncharuk, do you remember we planned to revisit the P2P as part of Ignite 3.0 to remove certain limitations? How about linking all the P2P tasks together and create either an

[jira] [Created] (IGNITE-12229) Column not found when using CASE named column from result

Ilya Kasnacheev created IGNITE-12229: Summary: Column not found when using CASE named column from result Key: IGNITE-12229 URL: https://issues.apache.org/jira/browse/IGNITE-12229 Project: Ignite

[jira] [Created] (IGNITE-12228) Implement an Apache Beam runner on top of Ignite compute grid?

Romain Manni-Bucau created IGNITE-12228: --- Summary: Implement an Apache Beam runner on top of Ignite compute grid? Key: IGNITE-12228 URL: https://issues.apache.org/jira/browse/IGNITE-12228

Re: [DISCUSSION] Single point in API for changing cluster state.

Sergey, +1, I like your idea. I think from the user point the INACTIVE -> READ-ONLY transition [1] should be allowed prior to adding a new `state` command [2] to avoid unnecessary error messages. I also think we can avoid the word 'set` in this command. Example: control.sh --state ACTIVE

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

Hello, Igniters. I want to notice one more blocker for release [1]. This bug can lead to some incorrect baseline default enabled flag calculation(more details in the ticket). [1] https://issues.apache.org/jira/browse/IGNITE-12227 --  Best regards, Anton Kalashnikov 24.09.2019, 17:01, "Andrey

[jira] [Created] (IGNITE-12227) Default auto-adjust baseline enabled flag calculated incorrectly in some cases

Anton Kalashnikov created IGNITE-12227: -- Summary: Default auto-adjust baseline enabled flag calculated incorrectly in some cases Key: IGNITE-12227 URL: https://issues.apache.org/jira/browse/IGNITE-12227

[jira] [Created] (IGNITE-12226) Improve BinaryObjectException message

Kirill Tkalenko created IGNITE-12226: Summary: Improve BinaryObjectException message Key: IGNITE-12226 URL: https://issues.apache.org/jira/browse/IGNITE-12226 Project: Ignite Issue Type:

Please grant jira-user privilege to me.

Hi dev, Right now I am working on https://issues.apache.org/jira/browse/IGNITE-11008 https://issues.apache.org/jira/browse/IGNITE-11868 https://issues.apache.org/jira/browse/IGNITE-12088 https://issues.apache.org/jira/browse/IGNITE-11976 most of them are ready for review. Can someone grant

Re: [IEP-35] Monitoring & Profiling. Phase 2

Alexey, Yes, system view must be enabled by default and must not have any enable/disable features. As I told early, system views is on demand feature and views don't consume any resources while not requested. On Wed, Sep 18, 2019 at 4:10 PM Alex Plehanov wrote: > > One more point to discuss:

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

Sergey, As I know, scope freeze is not announced yet. On Tue, Sep 24, 2019 at 4:41 PM Sergey Antonov wrote: > > Hi, I would add to release scope my ticket [1]. > > Any objections? > > [1] https://issues.apache.org/jira/browse/IGNITE-12225 > > вт, 24 сент. 2019 г. в 09:21, Nikolay Izhikov : > >

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

Alexey, > The planned before 2_3 months release dates are good defender from > partially merged features, In my opinion Agree. But it doesn't protect from cases when we have something in progress and partially merged to the master branch. > Or we should have Master and dev branch separetely,

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

Maxim, We can't do it because there is no strong rules about the process. But I have an idea how we can release 2.8 faster (but I still don't see any reasons for forcing release). We can create release branch before first IEP-35 related commit and cherry-pick all commits from master branch to

Re: [DISCUSSION] Single point in API for changing cluster state.

Andrey, > What are state transitions valid? Now all transitions are valid, except INACTIVE -> READ-ONLY. This transition will be fixed under [1] > Regarding state names, as I understand, all transitions are valid from any to any of 3 states. Yes, see my comment above. > But, regarding on

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

Hi, I would add to release scope my ticket [1]. Any objections? [1] https://issues.apache.org/jira/browse/IGNITE-12225 вт, 24 сент. 2019 г. в 09:21, Nikolay Izhikov : > > merge to master only fully finished features > > It's already true for Ignite master branch. > > > В Вт, 24/09/2019 в 09:03

Re: [DISCUSSION] Single point in API for changing cluster state.

Sergey, What are state transitions valid? For now we have only 2 states (active and inactive) and possible transitions are obvious Active <--> Inactive. Regarding state names, as I understand, all transitions are valid from any to any of 3 states. But, regarding on console.sh command it is not

Re: [DISCUSSION] Single point in API for changing cluster state.

Also, I would add IGNITE-12225 ticket to 2.8 release scope. вт, 24 сент. 2019 г. в 16:18, Sergey Antonov : > Hi, Igniters! > > We have 3 cluster states at the moment: inactive, active, read-only. > > For getting current cluster state and

[DISCUSSION] Single point in API for changing cluster state.

Hi, Igniters! We have 3 cluster states at the moment: inactive, active, read-only. For getting current cluster state and changing them IgniteCluster has methods: - boolean active(), void active(boolean active) - for cluster activation/deactivation - boolean readOnly(), void

[jira] [Created] (IGNITE-12225) Add enum for cluster state

Sergey Antonov created IGNITE-12225: --- Summary: Add enum for cluster state Key: IGNITE-12225 URL: https://issues.apache.org/jira/browse/IGNITE-12225 Project: Ignite Issue Type: Improvement

JavaDoc for Event's subjectId methods

Hello, Igniters! Some events contain the subjectId method, for example, TaskEvent#subjectId. The JavaDoc for this method is: "Gets security subject ID initiated this task event, if available. This property is not available for GridEventType#EVT_TASK_SESSION_ATTR_SET task event. Subject ID will be

Improvements for P2P class loading

Igniters! I would like to propose a few improvements for the P2P class loading feature in Ignite. These improvements have the aim to reduce the number of requests that may be needing to get a class on a remote node. a. We should send a request for a class to the node initiator firstly.

[jira] [Created] (IGNITE-12224) SQL query system view

Nikolay Izhikov created IGNITE-12224: Summary: SQL query system view Key: IGNITE-12224 URL: https://issues.apache.org/jira/browse/IGNITE-12224 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-12223) Create text query, scan query system view

Nikolay Izhikov created IGNITE-12223: Summary: Create text query, scan query system view Key: IGNITE-12223 URL: https://issues.apache.org/jira/browse/IGNITE-12223 Project: Ignite Issue

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

> merge to master only fully finished features It's already true for Ignite master branch. В Вт, 24/09/2019 в 09:03 +0300, Alexey Zinoviev пишет: > The planned before 2_3 months release dates are good defender from > partially merged features, In my opinion > > Or we should have Master and dev

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

The planned before 2_3 months release dates are good defender from partially merged features, In my opinion Or we should have Master and dev branch separetely, and merge to master only fully finished features пн, 23 сент. 2019 г., 20:27 Maxim Muzafarov : > Andrey, > > Agree with you. It can