Re: [ANNOUNCE] Welcome Kirill Tkalenko as a new committer
Congratulations, Kirill! > On 10 Oct 2022, at 17:15, Pavel Tupitsyn wrote: > > The Project Management Committee (PMC) for Apache Ignite > has invited Kirill Tkalenko to become a committer and we are pleased > to announce that they have accepted. > > Kirill is an active contributor and community member, he made significant > additions to Ignite 2.x and 3.x code bases, WAL and PageMemory improvements > among others. > > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > > Please join me in welcoming Kirill, and congratulating him on the new role > in > the Apache Ignite Community! > > Regards, > Pavel Tupitsyn
Re: [ANNOUNCE] Welcome Kirill Tkalenko as a new committer
Well deserved! On Mon, Oct 10, 2022 at 5:24 PM Kseniya Romanova wrote: > Kirill, congrats and welcome! > > пн, 10 окт. 2022 г. в 17:17, Roman Puchkovskiy < > roman.puchkovs...@gmail.com > >: > > > Congratulations, Kirill! > > > > пн, 10 окт. 2022 г. в 18:15, Pavel Tupitsyn : > > > > > > The Project Management Committee (PMC) for Apache Ignite > > > has invited Kirill Tkalenko to become a committer and we are pleased > > > to announce that they have accepted. > > > > > > Kirill is an active contributor and community member, he made > significant > > > additions to Ignite 2.x and 3.x code bases, WAL and PageMemory > > improvements > > > among others. > > > > > > Being a committer enables easier contribution to the > > > project since there is no need to go via the patch > > > submission process. This should enable better productivity. > > > > > > Please join me in welcoming Kirill, and congratulating him on the new > > role > > > in > > > the Apache Ignite Community! > > > > > > Regards, > > > Pavel Tupitsyn > > > -- With regards, Aleksandr Polovtcev
Re: [ANNOUNCE] Welcome Kirill Tkalenko as a new committer
Kirill, congrats and welcome! пн, 10 окт. 2022 г. в 17:17, Roman Puchkovskiy : > Congratulations, Kirill! > > пн, 10 окт. 2022 г. в 18:15, Pavel Tupitsyn : > > > > The Project Management Committee (PMC) for Apache Ignite > > has invited Kirill Tkalenko to become a committer and we are pleased > > to announce that they have accepted. > > > > Kirill is an active contributor and community member, he made significant > > additions to Ignite 2.x and 3.x code bases, WAL and PageMemory > improvements > > among others. > > > > Being a committer enables easier contribution to the > > project since there is no need to go via the patch > > submission process. This should enable better productivity. > > > > Please join me in welcoming Kirill, and congratulating him on the new > role > > in > > the Apache Ignite Community! > > > > Regards, > > Pavel Tupitsyn >
Re: [ANNOUNCE] Welcome Kirill Tkalenko as a new committer
Congratulations, Kirill! пн, 10 окт. 2022 г. в 18:15, Pavel Tupitsyn : > > The Project Management Committee (PMC) for Apache Ignite > has invited Kirill Tkalenko to become a committer and we are pleased > to announce that they have accepted. > > Kirill is an active contributor and community member, he made significant > additions to Ignite 2.x and 3.x code bases, WAL and PageMemory improvements > among others. > > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > > Please join me in welcoming Kirill, and congratulating him on the new role > in > the Apache Ignite Community! > > Regards, > Pavel Tupitsyn
[ANNOUNCE] Welcome Kirill Tkalenko as a new committer
The Project Management Committee (PMC) for Apache Ignite has invited Kirill Tkalenko to become a committer and we are pleased to announce that they have accepted. Kirill is an active contributor and community member, he made significant additions to Ignite 2.x and 3.x code bases, WAL and PageMemory improvements among others. Being a committer enables easier contribution to the project since there is no need to go via the patch submission process. This should enable better productivity. Please join me in welcoming Kirill, and congratulating him on the new role in the Apache Ignite Community! Regards, Pavel Tupitsyn
[ANNOUNCE] Apache Ignite 2.14.0 Released
The Apache Ignite Community is pleased to announce the release of Apache Ignite 2.14.0. Apache Ignite® is an in-memory computing platform for transactional, analytical, and streaming workloads delivering in-memory speeds at a petabyte scale. https://ignite.apache.org For the full list of changes, you can refer to the RELEASE_NOTES list which is trying to catalogue the most significant improvements for this version of the platform. https://ignite.apache.org/releases/2.14.0/release_notes.html Download the latest Ignite version from here: https://ignite.apache.org/download.cgi Please let us know if you encounter any problems: https://ignite.apache.org/community/resources.html#ask -- With best regards, Taras Ledkov
Re: [jira] [Assigned] (IGNITE-17857) The native client does not need to verify the configuration consistency of the DeploymentSpi
Hello, Is anyone willing to help check the ticket and merge the following PR? https://github.com/apache/ignite/pull/10297 在 2022/10/10 11:02, YuJue Li (Jira) 写道: [https://issues.apache.org/jira/browse/IGNITE-17857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] YuJue Li reassigned IGNITE-17857: - Assignee: YuJue Li The native client does not need to verify the configuration consistency of the DeploymentSpi Key: IGNITE-17857 URL:https://issues.apache.org/jira/browse/IGNITE-17857 Project: Ignite Issue Type: Improvement Components: clients Affects Versions: 2.14 Reporter: YuJue Li Assignee: YuJue Li Priority: Minor Fix For: 2.15 Attachments: IgniteClient.java, e.log, example-deploy.xml start a server node with example-deploy.xml by ignite.sh start a native client with IgniteClient.java then error. Normally, the client node does not need to verify the configuration consistency of the DeploymentSpi. Whether the client needs to configure DeploymentSpi should be decided by the user. -- This message was sent by Atlassian Jira (v8.20.10#820010)
