[MTCGA]: new failures in builds [5838760] 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 finalize

Re: [Discussion] Kanban board for quick start issues to join the community

I guess the same result could be achieved with simple labels, no? With regards, Cos On 22.01.2021 16:25, Saikat Maitra wrote: Hi, I was looking into our community page to find new open issues that I can contribute to and the easy and moderate tickets, tickets for beginners and SQL tasks help

Re: Contribution to Apache

Hello Igor, Welcome to the community! Hope you enjoy the contribution process and grow your expertise in both Ignite and distributed databases. I've added you to the contributors' list. So, go ahead and take over the ticket. - Denis On Fri, Jan 22, 2021 at 10:19 AM Игорь Барышников wrote: >

Re: Start contributing

Hello Alexey, Welcome aboard! You're in, I've added you to JIRA contributor's list. Look forward to your contribution! - Denis On Fri, Jan 22, 2021 at 12:46 AM Алексей wrote: > > Hi guys! > > My name is Alexey Plotnik, I'm a software engineer. > > I'd like to start contributing to Apache Igni

[MTCGA]: new failures in builds [5837597] 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 finalize

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Nikita, thanks. I reviewed those and shared some suggestions. Please take them into consideration. - Denis On Fri, Jan 22, 2021 at 1:45 PM Никита Сафонов wrote: > Hi everyone, > > The following documentation tasks for the important features now have PATCH > AVAILABLE status: > >- Caches wa

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Hi everyone, The following documentation tasks for the important features now have PATCH AVAILABLE status: - Caches warming up strategy - https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro - Update on JMX default configuration removal - https://issues.apache.org/jira/bro

[Discussion] Kanban board for quick start issues to join the community

Hi, I was looking into our community page to find new open issues that I can contribute to and the easy and moderate tickets, tickets for beginners and SQL tasks help me to find open issues to contribute. I am also thinking if we should use a project Kanban board in jira and move these issues in

Contribution to Apache

Hello everyone! My name is Igor Baryshnikov and I am a Java developer with four years of industry experience. I use Apache products from time to time so I thought it would be nice to contribute to the community. I would like to start with something simple like IGNITE-12724, so kindly ask you to g

Re: WAL enable/disable does not work on unstable topology - removal or warning

Hello! I have created a separate ticket for that work: https://issues.apache.org/jira/browse/IGNITE-14039 I have designated it as a blocker for 2.10 I have submitted a pull request. I will run tests: https://github.com/apache/ignite/pull/8688/files Mikhail, your approach makes sense. However, I d

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Hi All, Can you please also include a critical ticket https://issues.apache.org/jira/browse/IGNITE-13912 to 2.10 In terms of functionality it is a blocker. Still some debugging is going on related to this issue. Thanks, Shiva -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com

Re: [DISCUSSION] Apache Ignite Release 2.10 (time, scope, manager)

Hi everyone, I'm finishing my work on the documentation tasks for the following important features: - Caches warming up strategy - https://issues.apache.org/jira/browse/IGNITE-13385?src=confmacro - Update on JMX default configuration removal - https://issues.apache.org/jira/browse/IG

[jira] [Created] (IGNITE-14039) Add warnings about WAL enable/disable requiring topology stability

Ilya Kasnacheev created IGNITE-14039: Summary: Add warnings about WAL enable/disable requiring topology stability Key: IGNITE-14039 URL: https://issues.apache.org/jira/browse/IGNITE-14039 Project:

Re: [DISCUSS] Python thin client development approach.

Igor, I've never talked about complete removal of TC builds. I just suggested to add TC jobs for different python versions and use travis heavily. Currently, we have done most of the tasks, except of run TC tests on different python's versions. пт, 22 янв. 2021 г. в 15:16, Igor Sapego : > Ivan

[jira] [Created] (IGNITE-14038) Separate JVM settings in the ducktests.

Vladimir Steshin created IGNITE-14038: - Summary: Separate JVM settings in the ducktests. Key: IGNITE-14038 URL: https://issues.apache.org/jira/browse/IGNITE-14038 Project: Ignite Issue Ty

[jira] [Created] (IGNITE-14037) Separate JVM settings in the ducktests.

Vladimir Steshin created IGNITE-14037: - Summary: Separate JVM settings in the ducktests. Key: IGNITE-14037 URL: https://issues.apache.org/jira/browse/IGNITE-14037 Project: Ignite Issue Ty

Re: [DISCUSS] Python thin client development approach.

Ivan, Though I generally agree with the approach you've suggested, I can see a problem here. Since we now have a separate repos for thin clients, for some features we may need to introduce changes to Ignite and python-thin repos in a single ticket and we should have an ability to run tests on with

[jira] [Created] (IGNITE-14036) Tracing: add ability to trace compute operations.

Alexander Lapin created IGNITE-14036: Summary: Tracing: add ability to trace compute operations. Key: IGNITE-14036 URL: https://issues.apache.org/jira/browse/IGNITE-14036 Project: Ignite

[jira] [Created] (IGNITE-14035) Table access public API

Andrey Mashenkov created IGNITE-14035: - Summary: Table access public API Key: IGNITE-14035 URL: https://issues.apache.org/jira/browse/IGNITE-14035 Project: Ignite Issue Type: Sub-task

[jira] [Created] (IGNITE-14034) Calcite integration. indexCondition refactoring

Konstantin Orlov created IGNITE-14034: - Summary: Calcite integration. indexCondition refactoring Key: IGNITE-14034 URL: https://issues.apache.org/jira/browse/IGNITE-14034 Project: Ignite