Re: I want to contribute to Apache ignite
Hello! I've added you to the Contributors role - you may now assign tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 9 апр. 2024 г. в 20:13, Максим Михайлович Давыдов < davydov.m...@physics.msu.ru>: > Hello, Everyone! > > My name is Maksim. I want to contribute to Ignite. I would like to start > from IGNITE-21830. Please, help me to start contributing. > > My ASF JIRA username is mmdavydov > > Regards, > Maksim Davydov >
Re: I want to contribute to Apache ignite
Hello! You should now be able to assign issues to yourself - please check that. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev пт, 22 мар. 2024 г. в 10:42, Andrey : > Hello, Everyone! > > My name is Andrei. I want to contribute to Ignite. I would like to start > from IGNITE-21823. Please, help me to start contributing. > > My ASF JIRA username is andreinadyktov. > > Regards, > > Andrei. >
Re: I want to contribute to Apache ignite
Hello! I'm afraid you need to create a Confluence account separately. Regards, -- Ilya Kasnacheev чт, 1 февр. 2024 г. в 15:08, Vadim Kolodin : > Hello, Everyone! > > I have access to JIRA, but I can not log in to Ignite confluence > https://cwiki.apache.org/confluence/display/IGNITE. > I want to create IEP page related to > https://issues.apache.org/jira/browse/IGNITE-21410 > Please, help me to start contributing. > > My ASF JIRA username is vkolodin. > > -- > Regards, Vadim. >
Re: I want to contribute to Apache ignite 3
Hello! I've added you to Contributors role. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev ср, 31 янв. 2024 г. в 13:55, Vadim Kolodin : > Hello, Everyone! > > My name is Vadim. I want to contribute to Ignite 3. Please, help me to > start contributing. > > My ASF JIRA username is vkolodin. > > Regards, Vadim. >
Re: I want to contribute to Apache ignite
Hello! I've added you to Contributors, you may now assign tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev чт, 25 янв. 2024 г. в 10:55, Semen Zikunov : > Hello, Everyone! > My name is Semyon. I want to contribute to Ignite. Please, help me to > start contributing. > My ASF JIRA username is WyrdNEXUS. I want to start working as soon as > possible. I'll start with > https://issues.apache.org/jira/browse/IGNITE-19958 > Regards, > Semyon Zikunov
Re: I want to contribute to Apache ignite
Hello! I have added you to Contributors, you may now assign issues to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 23 янв. 2024 г. в 12:35, Viacheslav Blinov : > Hello, Everyone! > My name is Viacheslav Blinov. I want to contribute to Ignite. Please, help > me to start contributing. > My ASF JIRA username is vblinov. > > Regards, > Viacheslav Blinov
Re: I want to contribute to Apache Ignite
Hello! I have added you to Contributors role Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev пн, 22 янв. 2024 г. в 14:28, Philipp Shergalis : > Hello, Everyone! > > My name is Philipp, I'm a Software Engineer at Gridgain Systems and I want > to contribute to Ignite. > > My ASF JIRA account is fsherga...@gridgain.com > > Regards, > Philipp >
Re: I want to contribute to Apache ignite
Hello! I have added you to the Contributors role - you may now assign issues to yourself. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev пн, 15 янв. 2024 г. в 21:50, Mikhail Efremov : > Hello, Everyone! > My name is Mikhail. I want to contribute to Ignite. I would like to > start from IGNITE-15889. Please, help me to start contributing. > My ASF JIRA username is jakutenshi. > Regards, > Efremov Mikhail > >
Re: I want to contribute to Apache ignite
Hello! I have added you to Contributors role - you may now assign tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev ср, 20 дек. 2023 г. в 16:41, Artem Egorov : > Hello, Everyone! > > My name is Artem Egorov. I want to contribute to Ignite. I would like to > start from https://issues.apache.org/jira/browse/IGNITE-21128. Please, > help > me to start contributing. > > My ASF JIRA username is *artyeshi*. > > > Regards, > > Artem >
Re: I want to contribute to Apache ignite
Hello, Lokesh! I have added you to Contributors role - you may now assign tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute on the details. Regards, -- Ilya Kasnacheev ср, 8 нояб. 2023 г. в 03:47, loki : > Hello, Everyone! > > My name is Lokesh Chikka Kempanna. I want to contribute to Ignite. I would > like to start from IGNITE-17942 > <https://issues.apache.org/jira/browse/IGNITE-17942>. Please, help me to > start contributing. > > My ASF JIRA username is loki_kempanna > > Regards, > > Lokesh >
Re: I want to contribute to Apache ignite
Hello! I have created an account for you and assigned Contributor role - you may assign tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 7 нояб. 2023 г. в 14:27, daFomin : > Hello, Everyone! > > My name is Egor Fomin Alekseevich. I want to contribute to Ignite. I would > like to start from IGNITE-20737 > <https://issues.apache.org/jira/browse/IGNITE-20737>. Please, help me to > start contributing. > > I don't have a jira account yet even though I requested one 7 days ago, can > you help me get one? My email is fomin.ego...@gmail.com > > Regards, > > Egor Fomin Alekseevich >
Re: Ignite Eviction Policy Not Triggering Despite Proper Configuration
Hello! Please use userlist or stackoverflow to ask questions. Regards, -- Ilya Kasnacheev пн, 9 окт. 2023 г. в 10:40, Furkan Şahin : > Dear Apache Ignite Support Team, > > I hope this email finds you in good health. I am writing to seek assistance > regarding an issue I am currently encountering with Apache Ignite while > persisting data in memory. I have successfully set up Apache Ignite within > a Docker container, allocating 120GB of memory to the virtual machine. > Specifically, I have configured an off-heap memory of 80GB for Apache > Ignite in the configuration file. > > The relevant part of the configuration file pertaining to data storage is > as follows: > > > > > class="org.apache.ignite.configuration.DataRegionConfiguration"> > > > > > > > > > > > Despite configuring the eviction policy settings, I have observed that when > the Ignite memory usage approaches nearly 100%, the eviction process does > not initiate as expected. I have also attempted caching the data with a > TTL, but upon reviewing the Ignite logs, I noticed that there is no > increase in the freeRam percentage for the specified data region when the > data is destroyed. When the freeRam percentage approaches 0%, I am forced > to restart the container. > > I have tried implementing the suggested actions from the advisory message, > including increasing the maximum off-heap memory size and enabling Ignite > persistence and eviction or expiration policies. However, these actions did > not resolve the issue. > > I would greatly appreciate your assistance in enabling the eviction policy > to function effectively and initiating eviction when the Ignite memory > usage approaches the specified threshold. If there are any additional > solutions or insights from the documentation regarding this matter, please > do share them. > > Thank you for your time and support. I look forward to your guidance. > > Best regards, > > Furkan Sahin >
Re: I want to contribute to Apache ignite
Hello! I have added you to the Contributors role. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev ср, 4 окт. 2023 г. в 13:45, YaFeng <1491087...@qq.com.invalid>: > Hello, Everyone! > My name is Yafeng. I want to contribute to Ignite. I would like to start > from [https://issues.apache.org/jira/browse/IGNITE-20552]. Please, help > me to start contributing. > My ASF JIRA username is yafengshi. > Regards, > Yafeng
Re: I want to contribute to Apache ignite
Hello! Account created, issue assigned. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev чт, 21 сент. 2023 г. в 12:10, Анастасия Якимова : > Hello, Everyone! > > My name is Iakimova Anastasia. I want to contribute to Ignite. I would like > to start from https://issues.apache.org/jira/browse/IGNITE-20426. > > Please, help me to start contributing. > > My ASF JIRA username is AnNYakimova. > > Regards, > > Iakimova Anastasia. >
Re: I want to contribute to Apache ignite
Hello! I have added you to the Contributors role. You may now assign issues to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev сб, 19 авг. 2023 г. в 10:28, Wei Cheng <29608336...@gmail.com>: > >> Hello, Everyone! > >> > >> > >> My name is Wei Cheng. I want to contribute to Ignite. I would like to > start with the issue of modifying the program. Please, help me to start > contributing. > >> My ASF JIRA username is arlon. >
Re: Contribution to Apache Ignite
Hello! That is now done. I have removed that other one Zlenko from contributors. I hope he doesn't mind. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev ср, 9 авг. 2023 г. в 10:32, Ivan Zlenko : > Hi, Ilya. > My account for this project is ivan.zlenko > <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ivan.zlenko>. > Sincerely yours, > Ivan Zlenko. > > On Tue, Aug 8, 2023 at 9:34 PM Ilya Kasnacheev > wrote: > > > Hello! > > > > We've noticed that you have requested a new account creation. > > > > Can you please tell me which one of these is yours: > > https://issues.apache.org/jira/secure/ViewProfile.jspa?name=izlenko vs. > > https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ivan.zlenko > > (new > > account). > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 8 авг. 2023 г. в 17:27, Ivan Zlenko : > > > > > Hello Ignite community! > > > My name is Ivan. I've recently started contributing to Apache Ignite > and > > > want to have a contributor role on Jira or something similar so I can > > > manage issue's statuses which I'm working on right now. My recent > ticket > > is > > > IGNITE-19953 <https://issues.apache.org/jira/browse/IGNITE-19953> and > I > > > have a pull request available already. > > > Any help would be greatly appreciated. > > > Sincerely yours, > > > Ivan Zlenko. > > > > > >
Re: Contribution to Apache Ignite
Hello! We've noticed that you have requested a new account creation. Can you please tell me which one of these is yours: https://issues.apache.org/jira/secure/ViewProfile.jspa?name=izlenko vs. https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ivan.zlenko (new account). Regards, -- Ilya Kasnacheev вт, 8 авг. 2023 г. в 17:27, Ivan Zlenko : > Hello Ignite community! > My name is Ivan. I've recently started contributing to Apache Ignite and > want to have a contributor role on Jira or something similar so I can > manage issue's statuses which I'm working on right now. My recent ticket is > IGNITE-19953 <https://issues.apache.org/jira/browse/IGNITE-19953> and I > have a pull request available already. > Any help would be greatly appreciated. > Sincerely yours, > Ivan Zlenko. >
Re: Questions about Ignite's Cache and SQL Modules
Hello! Please use Stack Overflow or users list to ask questions - developers list is for the development efforts of Ignite itself. Regards, -- Ilya Kasnacheev чт, 20 июл. 2023 г. в 03:16, ZhangJian He : > Hello, community. My name is ZhangJian He and I'm currently using Apache > Ignite organization. > > I am interested in knowing if data stored in the Cache module can be > queried using Ignite's SQL module and vice versa? > > Any help will be appreciated. > > Thanks > ZhangJian He >
Re: I want to contribute to Apache ignite
Hello! I have added you to the Contributors role - you may now assign issues to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev чт, 13 июл. 2023 г. в 14:24, Дмитрий Баранов : > Hello, Everyone! > > My name is Dmitry Baranov. I want to contribute to Ignite. I would like to > start from some improvements in CLI > https://issues.apache.org/jira/browse/IGNITE-19108. Please, help me to > start contributing. > > My ASF JIRA username is dmitry.baranov. > > Regards, > > Dmitry Baranov >
Re: I want to contribute to Apache ignite
Hello! Should be already done - please try assigning tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 4 июл. 2023 г. в 15:14, Kirill Sizov : > Hello apache devs, > I would like to contribute to the project. Could you add me to the > Contributors group in JIRA please? My Apache JIRA username is ksizov. > > Kind regards, > Kirill Sizov >
Re: Jira access request
Hello! I have approved a JIRA account creation and added you to Contributors role - you may now assign tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev пт, 30 июн. 2023 г. в 23:13, Ehsan Kiani Far : > Hello Ignite Community! > > My name is Ehsan Kiani Far. As a software developer and Ignite user I have > a few ideas to improve Ignite and would like to share those with the > community. I requested Jira access with username: ehsankianifar and > appreciate it if the community approves my request. Thanks! > > Best wishes, > Ehsan Kiani Far >
Re: I want to contribute to Apache ignite
Hello! I have added you to the 'contributors' role - you may now assign tickets to yourself. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 13 июн. 2023 г. в 11:24, LonesomeRain : > Hello, Everyone! > > My name is Mengyu Jing. I want to contribute to Ignite. I would like to > start from ignite-core. Please, help me to start contributing. > My ASF JIRA username is lonesomerain. > > Regards, > Mengyu Jing >
Re: [DISCUSSION] IEP-107 Logging in Ignite 3
Hello! Even apart from testing, it is not uncommon to have JVM connect two different Ignite clusters (two heterogenous ones or one main cluster and the second "management" small cluster, for example) Regards, -- Ilya Kasnacheev вт, 13 июн. 2023 г. в 12:46, Konstantin Orlov : > Hi Ilya, > > I wonder why do you try to run several Ignite instances in the same JVM in > the first place? Is there any value to do so, apart for testing? > > Anyway, with current proposal you could try to configure message routing > based on a thread name: every thread in Ignite 3 should have name which > starts with "%%” prefix. > > -- > Regards, > Konstantin Orlov > > > > > > On 8 Jun 2023, at 18:14, Ilya Korol wrote: > > > > Hi Konstantin. Thanks for you work. > > > > Despite you proposal is more about public API of logging Ignite > facility, I believe that this thread is the best place to highlight some > topic about internal details of IgniteLogger based on my experience with > Ignite 2 > > > > I already tried to initiate a discussion at the end of previous year, > unfortunately there were not so many community members eager to discuss it. > > > > Here is the link > https://lists.apache.org/thread/xcllwbz12cpb5437hrt5n1xfdfp0wqct > > > > The feature, that from my perspective, is missing in current > implementation (AI2) and that should be kept in mind when it comes to > implement logging IEP, > > is ability to separate messages produced by different Ignite instances > running in same JVM, > > so at appenders level (no matter of the actual logging implementation) > there is no way to properly route log messages to separate locations based > on the message source node. > > > > Maybe community will find this feature useful. > > > > > > > > On 08.06.2023 17:45, Konstantin Orlov wrote: > >> Hi, > >> > >> Please review "IEP-107 Logging in Ignite 3” proposal > >> > >> > https://cwiki.apache.org/confluence/display/IGNITE/IEP-107+Logging+in+Ignite+3 > >> > >> > >> -- > >> Regards, > >> Konstantin Orlov > >> > >> > >> > >> > >> > >
Re: How to access ignite cluster outside Kubernetes?
Hello! This is not appropriate for dev list (try user@ or SO) but short answer, for thin client use ClientConnectorConfiguration, and thick client is not going to work. Regards, -- Ilya Kasnacheev чт, 1 июн. 2023 г. в 06:35, Rahul Ranjan : > Hi, > > I have deployed an ignite cluster on the kubernetes environment (GKE). Have > created k8s ingress for thinclient coonection. > My local app (which is outside the k8s env) needs to connect to this ignite > cluster . > > Have tried using the following snippet. This is not working for thinClient > using ignite-core and ignite-client library (version 2.14.0) > > String url = ingress_url > > ClientConfiguration cfg = new ClientConfiguration().setAddresses(url); > > Could you please suggest how to connect (*thinclient*) to the ignite > cluster, from outside the k8s environment. > > > Thanks, > > Rahul Ranjan > > On Wed, 31 May 2023 at 21:32, Rahul Ranjan > wrote: > > > Hi, > > > > I have deployed ignite cluster on kubernetes environment (GKE). Have > > created k8s ingress for thinclient . > > My local app needs to connect this ignite cluster . > > > > String url = ingress_url > > > > ClientConfiguration cfg = new ClientConfiguration().setAddresses(url); > > > > This is not working for thinClient using ignite-core and ignite-client > > library (version 2.14.0) > > > > > > Thanks, > > > > Rahul Ranjan > > > > > > >
Re: I want to contribute to Apache ignite if possbile
Hello! Are there any specific JIRA or GitHub issues that you want to take on? If there aren't, I suggest checking out the project, accustomizing with building it. Regards, -- Ilya Kasnacheev вт, 2 мая 2023 г. в 16:16, David Kuang : > Hi all! > > My name is David Kuang. I would like to learn from and contribute to Ignite > if possible. Please kindly let me know what I should do next, thanks! > > Thank you! > > *David Kuang* > > Tel: +1 716-580-5481 > > Email: davidkuang...@gmail.com >
Re: Apache Ignite 2.15 RELEASE [Time, Scope, Manager]
+1! -- Ilya Kasnacheev ср, 29 мар. 2023 г. в 23:13, Vladimir Steshin : > +1 > > 29.03.2023 21:56, Alex Plehanov пишет: > > Dear Ignite Community! > > > > I suggest starting Apache Ignite 2.15 release activities. > > > > We've accumulated more than two hundred resolved issues [1] with new > > features and bug fixes which are waiting for release. > > The major changes related to the proposed release: > > - Incremental snapshots. > > - Java thin client improvements (logging, connections balancing, > > events listening, endpoints discovery) > > - Calcite based SQL engine improvements (memory quotas, index scans > > optimisations). > > - Reworked permission management for system tasks. > > - Removed some deprecated functionality (daemon nodes, visorcmd, legacy > JMX > > beans) > > etc. > > > > I want to propose myself to be the release manager of the planning > release. > > > > I propose the following timeline: > > > > Scope Freeze: April 08, 2023 > > Code Freeze: April 15, 2023 > > Voting Date: April 22, 2023 > > Release Date: April 29, 2023 > > > > [1]. > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20in%20(2.15))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27) > > > > WDYT? > > >
Re: JIRA Ticket - IGNITE-18875.
Hello! I have added you to Contributors role - you may now assign tickets to yourself. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev ср, 29 мар. 2023 г. в 00:26, Gael Yimen Yimga : > Hello Ignite Community! > > My name is Gael. I want to contribute to Apache Ignite and want to start > with this issue - IGNITE-18875, my JIRA username yimengael. Any help on > this will be appreciated. > > Thanks! > -- > Gael. >
Re: Setting up the project locally.
Hello! You may just import it into IntelliJ IDEA or run mvn clean install -DskipTests. Regards, -- Ilya Kasnacheev пн, 27 мар. 2023 г. в 18:49, Gael Yimen Yimga : > Hello, > > Please I'm looking for the documentation to set up the project on my local > machine so that I can start the development. I thought I would be able to > find it in the README.md <https://github.com/apache/ignite>, but not. > Please correct me if I'm wrong. > > Thanks for your help. > Gael. > -- >
Re: I want to contribute to Apache ignite
Hello! I have added you to Contributors role, but I'm not sure how to help you picking ticket. Do you want to work on Ignite 3 or improve Ignite 2? Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вс, 22 янв. 2023 г. в 07:50, kamalesh palanisamy : > Hello, Everyone! > > My name is Kamalesh P. I want to contribute to Ignite. I am not sure what > issue to get started with. Can you help me choose an issue? Thanks! > > My ASF JIRA username is kamalesh0420. > > Regards, > Kamalesh P >
Re: Creatng a Jira account
Hello! I've created derr22 account for you and added it to Contributors role. Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 6 дек. 2022 г. в 12:33, Данил Манмарёв : > Hello > > Thanks for a very fast answer > Any of following, if it suits: > derr22 > danr428 > > Thanks. > > > > Best regards, > Manmarev Danil > > > On Mon, Dec 5, 2022 at 11:48 PM Ilya Kasnacheev > wrote: > >> Hello! >> >> Sure! What's your preference for a user name? >> >> Regards, >> -- >> Ilya Kasnacheev >> >> >> пн, 5 дек. 2022 г. в 17:04, Данил Манмарёв : >> >>> Hello. >>> >>> I would like to ask for the creation of an account for Jira, which will >>> be used for Ignite Jira Project >>> <https://issues.apache.org/jira/projects/IGNITE>. >>> >>> Thanks in advance. >>> >>> >>> Best regards, >>> Manmarev Danil >>> >>
Re: Creatng a Jira account
Hello! Sure! What's your preference for a user name? Regards, -- Ilya Kasnacheev пн, 5 дек. 2022 г. в 17:04, Данил Манмарёв : > Hello. > > I would like to ask for the creation of an account for Jira, which will be > used for Ignite Jira Project > <https://issues.apache.org/jira/projects/IGNITE>. > > Thanks in advance. > > > Best regards, > Manmarev Danil >
Re: [DISCUSSION] Removal of ignitevisorcmd
Hello! Let's go ahead and remove what we don't use. Most of that stuff is deep legacy, even if it contains some rare gems of functionality that nobody knows how to use anymore. Regards, -- Ilya Kasnacheev ср, 30 нояб. 2022 г. в 20:12, Nikolay Izhikov : > Hello, Igniters. > > There are legacy modules - visor-console, visor-plugins, visor-console-2.10 > Looks like that modules are not evolving by community and barely used by > the Ignite users. > > I propose to remove it completely. > There are IEP [1] for this > > It seems that removal of visor modules allow to us to remove another legacy > code from Ignite codebase: > > * support of daemon nodes. > * GridClient and related classes. > > What do you think? > > [1] > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=217392419 >
Re: Apache JIRA account request
Hello! I have created an account for you and also added you to Ignite Contributors role. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev ср, 30 нояб. 2022 г. в 19:44, Ilkhom Ulmasov : > Dear Ignite team, > > May I have an Apache JIRA account to be able to work with Ignite tickets? > > My email ilhom.ulma...@gmail.com > Preferred user name is (iulmasov or imulmasov) > Display name is Ilhom Ulmasov > > BR, Ilhom >
Re: Please add me to the devlist
Hello! I have created a JIRA account for you (alexlev). Please try if you can create Confluence account. I have added you to Contributors role. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev пн, 21 нояб. 2022 г. в 19:52, Alex Levitski : > Hello Igniters, > I would like to contribute to Ignite. Could you please add me to ASF Jira > and Confluence as a contributor. My preferred user name is AlexLev-Ignite. > I will follow the rules described in “How to Contribute, Jira process.” > Thanks in advance! > Cheers, > Alex Levitski >
Re: Ignite OpenSSL Vulnerability
Hello! For the most part, we to not supply compiled versions of our C++ code, and our Java code does not use OpenSSL. So you should check if you can build ODBC driver against non-affected OpenSSL version. Regards, -- Ilya Kasnacheev чт, 3 нояб. 2022 г. в 15:45, Entwicklung : > Hello, > > i hope i use the correct email address. > > (u...@ignite.apache.org<mailto:u...@ignite.apache.org> returned wrong > email address.) > > > > I plan to install Apache Ignite version 2.14.0 binary release (latest) on > a windows server. I prefer ODBC-Connection to my application. > > > > Problem: > > ODBC uses OpenSSL, but Version 3.0.0 to 3.0.6 has critical vulnerability. > Version 3.0.7 has fixed the problems. Is 2.14.0 binary release (especially > ODBC) affected ? If yes, when is a new binary release available with > OpenSSL 3.0.7. > > I could not find any information about the OpenSSL version that Ignite > binaries were built from, especially ODBC. > > > > Thank you for your help > Regards > Guido Clesius > __ > Dipl.-Ing. Guido Clesius > Externer Mitarbeiter > Softwareentwicklung Guido Clesius > Im Sand 1 > 55252 Mainz-Kastel > * 06134-9589649 > Ë 0170-4430211 > * supp...@swe-clesius.de<mailto:supp...@swe-clesius.de> > þwww.swe-clesius.de<http://www.swe-clesius.de/> > > > > > > > > >
Re: Request for contribution permissions for Apache Ignite project
Hello! Please provide your JIRA id. Regards, -- Ilya Kasnacheev чт, 27 окт. 2022 г. в 15:46, Владимир Корнышев : > > Please, give me permissions for contributing to Apache Ignite project > > --- > Best regards, > Корнышев Владимир. > > ...Но если восстанут боги с громами наперевес, > Как пепел от сигареты, богов отряхнут с небес, > Пушки забьются в злобе, залают громам в ответ, > И в небе оставят боги извилистый дымный след!
Re: [Sugestion] Switching ignite scheduler to cron-utils
Hello! I suggest getting rid of ignite scheduler completely. It is poorly thought out, not used by anyone, has a baroque and incomplete API. In no way it is doing anything useful for out users in its current form. Yes we could rewrite it to be more useful, but I think Ignite is not a distributed scheduling system. We have too much on our plate already. If anybody wants to create a robust scheduler based on Ignite, they are free to do so in a dedicated project. I think we had consensus to drop it but just too lazy to complete that process. Regards, -- Ilya Kasnacheev пн, 17 окт. 2022 г. в 18:54, Łukasz Dywicki : > One of projects I recently worked with found a ASLv2 compatible library > which allows to parse CRON expressions and host scheduler calls: > https://github.com/jmrozanec/cron-utils > > Maybe it could help making ignite library/license handling more consistent. > > Best, > Łukasz >
Re: Question
Hello! Questions about Ignite usage should be asked on userlist (user@) or on Stack Overflow. Regards, -- Ilya Kasnacheev ср, 12 окт. 2022 г. в 14:59, Wadhe, Amit Pralhad : > Hi Team, > > Want to understand what could be possible scenarios where below exception > can arise? > > Exception while consuming the event: Failed to map SQL query to topology > on data node [dataNodeId=36538e74-7ab8-4598-80f4-d7131bde18d2, msg=Data > node has left the grid during query execution > [nodeId=36538e74-7ab8-4598-80f4-d7131bde18d2]] > > > Thanks, > Amit Wadhe > > > > This message may contain confidential information protected by law. The > contents of this email are to be viewed only by the intended recipient. If > you received this message in error, notify the sender immediately and > delete the original message without printing. Product descriptions, pricing > and similar content is for information only and does not constitute an > offer, warranty or guarantee. Contracts with Arcesium are formed only by > written documents bearing the signature of its authorized representative. > >
Re: [VOTE] Release Apache Ignite 2.14.0 RC0
0 (binding) If the main point of this release is Calcite, maybe we should make effort to demonstrate it is queryable without legacy ignite-indexing? But I'm not going to force this matter. -- Ilya Kasnacheev пн, 3 окт. 2022 г. в 14:06, Maxim Muzafarov : > +1 (binding) > > On Mon, 3 Oct 2022 at 14:05, Ivan Daschinsky wrote: > > > > +1 (binding) > > > > Checked C++ module and C++ examples compilation on windows 10 (msvc 2017) > > and ubuntu 22.04 (gcc 11.2.0). > > Checked ODBC on windows 10 and ubuntu 22.04 (unixodbc) by pyodbc and > python > > script (both H2 and CALCITE query engines). > > Checked ODBC pre-built binaries on windows 10 > > > > Despite the fact that separation of H2 and CALCITE has been announced, H2 > > (ignite-indexing) is still required for ODBC and CALCITE queries. > > Created issue for it -- > https://issues.apache.org/jira/browse/IGNITE-17800 > > > > > > пн, 3 окт. 2022 г. в 13:42, mwiesenberg : > > > > > +1 > > > started a node with calcite, inserted data, ran a sql query. > > > > > > On Mon, Oct 3, 2022 at 2:46 AM Pavel Tupitsyn > > > wrote: > > > > > > > +1 > > > > > > > > Started .NET and Java nodes, checked examples, checked NuGet > packages. > > > > > > > > On Fri, Sep 30, 2022 at 4:07 PM Alex Plehanov < > plehanov.a...@gmail.com> > > > > wrote: > > > > > > > > > > Added new experimental, Apache Calcite based SQL engine > > > > > It was added in 2.13, in 2.14 it became ignite-indexing (and H2) > > > > > independent. > > > > > > > > > > +1 > > > > > > > > > > Build from sources, start a cluster of two nodes, try some queries > on > > > > > Calcite SQL engine (with removed ignite-indexing module). > > > > > > > > > > пт, 30 сент. 2022 г. в 15:02, Zhenya Stanilovsky > > > > > > > > > >: > > > > > > > > > > > > > > > > > > > > > > > I think it`s important to mention that local caches are not > supported > > > > > > since this version [1]. > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15759 > > > > > > > > > > > > > > > > > > >Dear Community, > > > > > > > > > > > > > >The release candidate is ready. > > > > > > > > > > > > > >I have uploaded release candidate to > > > > > > >https://dist.apache.org/repos/dist/dev/ignite/2.14.0-rc0/ > > > > > > > > https://dist.apache.org/repos/dist/dev/ignite/packages_2.14.0-rc0/ > > > > > > > > > > > > > >The following staging can be used for testing: > > > > > > > > > > > > > > > > https://repository.apache.org/content/repositories/orgapacheignite-1552/ > > > > > > > > > > > > > >Tag name is 2.14.0-rc0: > > > > > > > > > > > > > > > > > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.14.0-rc0 > > > > > > > > > > > > > >2.14.0 most important changes: > > > > > > >* Added new experimental, Apache Calcite based SQL engine > > > > > > >* Added support of IGNITE_TO_STRING_INCLUDE_SENSITIVE option by > > > > > > Сonsistency check command > > > > > > >* CPP Thin: Implemented asynchronous network events handling > > > > > > >* CPP thin: Implemented continuous queries > > > > > > >* Deprecated IgniteServices#service(String) and > > > > > > IgniteServices#services(String). > > > > > > >* Implemented CDC for in-memory caches > > > > > > >* Implemented NUMA aware allocator for Ignite durable memory > > > > > > >* Implemented Read Repair strategies > > > > > > >* Implemented array component type in binary object > > > > > > >* Removed the legacy service grid implementation > > > > > > > > > > > > > >RELEASE NOTES: > > > > > > > > > > > > > > > > > > > > > > > > > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEA
Re: [VOTE] Ignite Packaging IEP
Hello! Please clarify whether this is Apache Ignite 3 only and that it does not affect Apache Ignite 2.x (or does it?) Thanks, -- Ilya Kasnacheev пн, 22 авг. 2022 г. в 16:07, Mikhail Pochatkin : > Hi Igniters, > > I want to start a voting process about several points from IEP-93 [1]. > > 1. Switch Apache Ignite build system to Gradle as default. > 2. Consequently, after changing the build system to Gradle we need to add > new third party dependencies to several Gradle plugins. This is list of new > complete time deps: > openapiGenerator = "org.openapi.generator:5.4.0" > javacc = "com.intershop.gradle.javacc:4.0.1" > launch4j = "edu.sc.seis.launch4j:2.5.3" > shadow = "com.github.johnrengelman.shadow:7.1.2" > cmake = "io.github.tomtzook.gradle-cmake:1.0.0" > jreleaser = "org.jreleaser:1.1.0" > 3. Agreement on all target package formats for Apache Ignite distributions. > > The vote is formal, see voting guidelines [3]. > > +1 - to accept all points above > 0 - don’t care either way > -1 - DO NOT accept (explain why) > > This vote will be open for at least 4 days till Friday Aug 26, 2022, > 22:00 Moscow TZ. > > [1] > > https://cwiki.apache.org/confluence/display/IGNITE/IEP-93%3A+Ignite+Packaging > [2] https://www.apache.org/foundation/voting.html >
Re: Travis. Error accessing to the file
Hello! Sometimes files in .m2 local repo become corrupted, just remove the offending directory /home/travis/.m2/repository/org/apache/hadoop/thirdparty/hadoop-shaded-guava/1.1.1 Regards, -- Ilya Kasnacheev пт, 12 авг. 2022 г. в 14:35, Ivan Gagarkin : > Hi, Igniters > I created a pull request, but the build failed with the next error > > > [ERROR] error: scala.reflect.internal.FatalError: Error accessing > /home/travis/.m2/repository/org/apache/hadoop/thirdparty/hadoop-shaded-guava/1.1.1/hadoop-shaded-guava-1.1.1.jar > > [INFO]at > scala.tools.nsc.classpath.AggregateClassPath.$anonfun$list$3(AggregateClassPath.scala:113) > > [INFO]at scala.collection.Iterator.foreach(Iterator.scala:943) > > [INFO]at scala.collection.Iterator.foreach$(Iterator.scala:943) > > [INFO]at > scala.collection.AbstractIterator.foreach(Iterator.scala:1431) > > [INFO]at > scala.collection.IterableLike.foreach(IterableLike.scala:74) > > [INFO]at > scala.collection.IterableLike.foreach$(IterableLike.scala:73) > > [INFO]at > scala.collection.AbstractIterable.foreach(Iterable.scala:56) > > [INFO]at > scala.tools.nsc.classpath.AggregateClassPath.list(AggregateClassPath.scala:101) > > [INFO]at scala.tools.nsc.util.ClassPath.list(ClassPath.scala:36) > > [INFO]at scala.tools.nsc.util.ClassPath.list$(ClassPath.scala:36) > > [INFO]at > scala.tools.nsc.classpath.AggregateClassPath.list(AggregateClassPath.scala:30) > > [INFO]at > scala.tools.nsc.symtab.SymbolLoaders$PackageLoader.doComplete(SymbolLoaders.scala:298) > > [INFO]at > scala.tools.nsc.symtab.SymbolLoaders$SymbolLoader.complete(SymbolLoaders.scala:250) > > [INFO]at > scala.reflect.internal.Symbols$Symbol.completeInfo(Symbols.scala:1542) > > [INFO]at > scala.reflect.internal.Symbols$Symbol.info(Symbols.scala:1514) > > [INFO]at > scala.reflect.internal.Mirrors$RootsBase.init(Mirrors.scala:258) > > [INFO]at > scala.tools.nsc.Global.rootMirror$lzycompute(Global.scala:75) > > [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:73) > > [INFO]at scala.tools.nsc.Global.rootMirror(Global.scala:45) > > [INFO]at > scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass$lzycompute(Definitions.scala:294) > > [INFO]at > scala.reflect.internal.Definitions$DefinitionsClass.ObjectClass(Definitions.scala:294) > > [INFO]at > scala.reflect.internal.Definitions$DefinitionsClass.init(Definitions.scala:1504) > > [INFO]at scala.tools.nsc.Global$Run.(Global.scala:1214) > > [INFO]at scala.tools.nsc.Driver.doCompile(Driver.scala:46) > > [INFO]at scala.tools.nsc.MainClass.doCompile(Main.scala:32) > > [INFO]at scala.tools.nsc.Driver.process(Driver.scala:67) > > [INFO]at scala.tools.nsc.Driver.main(Driver.scala:80) > > [INFO]at scala.tools.nsc.Main.main(Main.scala) > > [INFO]at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > > [INFO]at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > > [INFO]at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > > [INFO]at java.lang.reflect.Method.invoke(Method.java:498) > > [INFO]at > scala_maven_executions.MainHelper.runMain(MainHelper.java:164) > > [INFO]at > scala_maven_executions.MainWithArgsInFile.main(MainWithArgsInFile.java:26) > > [ERROR] Caused by: java.io.IOException: Error accessing > /home/travis/.m2/repository/org/apache/hadoop/thirdparty/hadoop-shaded-guava/1.1.1/hadoop-shaded-guava-1.1.1.jar > > [INFO]at scala.reflect.io > .FileZipArchive.scala$reflect$io$FileZipArchive$$openZipFile(ZipArchive.scala:190) > > [INFO]at scala.reflect.io > .FileZipArchive.root$lzycompute(ZipArchive.scala:238) > > [INFO]at scala.reflect.io > .FileZipArchive.root(ZipArchive.scala:235) > > [INFO]at scala.reflect.io > .FileZipArchive.allDirs$lzycompute(ZipArchive.scala:272) > > [INFO]at scala.reflect.io > .FileZipArchive.allDirs(ZipArchive.scala:272) > > [INFO]at > scala.tools.nsc.classpath.ZipArchiveFileLookup.findDirEntry(ZipArchiveFileLookup.scala:76) > > [INFO]at > scala.tools.nsc.classpath.ZipArchiveFileLookup.list(ZipArchiveFileLookup.scala:63) > > [INFO]at > scala.tools.nsc.classpath.ZipArchiveFileLookup.list$(ZipArchiveFileLookup.scala:62) > > [INFO]at > scala.tools.nsc.classpath.ZipAndJarClassPathFactory$ZipArchiveClassPath.list(ZipAndJarFileLook
Re: Contributor access
Hello! I have added you to JIRA and Wiki as contributor. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 2 авг. 2022 г. в 15:57, Ivan Gagarkin : > Hello igniters, > > I’d like to contribute to Ignite, could you please add me to ASF Jira and > Confluence as a contributor. > > -- > Best regards, Ivan Gagarkin >
Re: [jira] [Assigned] (IGNITE-17432) ignitevisorcmd can't run in jdk17 env
Hello, I have approved the PR. Regards, -- Ilya Kasnacheev чт, 28 июл. 2022 г. в 06:50, 18624049226 <18624049...@163.com>: > Hello, > > Is there anyone willing to help merge the following PR? > > https://github.com/apache/ignite/pull/10173 > > 在 2022/7/28 11:35, YuJue Li (Jira) 写道: > > [ > https://issues.apache.org/jira/browse/IGNITE-17432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > ] > > > > YuJue Li reassigned IGNITE-17432: > > - > > > > Assignee: YuJue Li > > > >> ignitevisorcmd can't run in jdk17 env > >> - > >> > >> Key: IGNITE-17432 > >> URL:https://issues.apache.org/jira/browse/IGNITE-17432 > >> Project: Ignite > >> Issue Type: Bug > >> Components: cli > >> Affects Versions: 2.13 > >> Reporter: YuJue Li > >> Assignee: YuJue Li > >> Priority: Minor > >> Fix For: 2.14 > >> > >> > >> Unrecognized VM option 'MaxPermSize=128M' > >> Error: Could not create the Java Virtual Machine. > >> Error: A fatal exception has occurred. Program will exit. > > > > > > -- > > This message was sent by Atlassian Jira > > (v8.20.10#820010)
Re: Re: Question about the sources of the Apache Ignite version 2.12.0-1
Hello! AFAIK all rpm packages have -N postfix by convention which is the build number of corresponding rpm package of a given version. I think we're using rpm to deb (?) so it is carried over to deb. So -1 is just stock 2.12.0 built from the first try. In case we would screw the packaging we would release 2.12.0-2, etc. Regards, -- Ilya Kasnacheev чт, 30 июн. 2022 г. в 23:46, Koltermann, BENJAMIN < benjamin.kolterm...@siemens.com>: > Hi, > Thanks for your answer. > I mean the DEB build. In the changelog here ( > https://github.com/apache/ignite/blob/master/packaging/deb/changelog ) is > written 2.12.0-1. What means the "-1"? Is this another version? > Kind regards > Benjamin > > > On 2022/06/21 16:30:37 Николай Ижиков wrote: > > Hello. > > > > Apache Ignite doesn't have version 2.12.0-1 > > > > https://ignite.apache.org/download.cgi < > https://ignite.apache.org/download.cgi> - here you can find existing > releases. Links to source archives provided, also. > > > > > https://github.com/apache/ignite/tags < > https://github.com/apache/ignite/tags> - same sources on GitHub. > > > > > 17 июня 2022 г., в 16:53, Koltermann, BENJAMIN > написал(а): > > > > > > Hi Apache Ignite Dev Team, > > > > > > I have a question to the sources of the Apache Ignite build 2.12.0-1. > Which sources were used for the build. Were the same sources used as in > version 2.12.0 or is there a difference? > > > > With best regards, > > > Benjamin Koltermann > > > > > > Siemens Mobility GmbH > > > SMO RI ML ADC ETCS AR > > > Ackerstr. 22 > > > 38126 Braunschweig, Germany > > > Mobile: +49 (173) 4147755 > > > mailto:benjamin.kolterm...@siemens.com > > > www.siemens.com > > > > > > Siemens Mobility GmbH; Chairman of the Supervisory Board: Roland > Busch; Management Board: Karl Blaim, Michael Peter; Registered office: > Munich, Germany; Commercial registry Munich, HRB 237219; WEEE-Reg.-No. DE > 92917817 > > > > > >
Re: Contributor permissions request
Hello! I have added you to JIRA and Wiki Please read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev чт, 2 июн. 2022 г. в 17:05, Timur Magomedov : > Hello, > I'd like to contribute to Apache Ignite. Could you please grant me > contributor permissions for Jira and Confluence? > My username is tmagomedov on both of them. > > Thanks, > Timur Magomedov. >
Re: [VOTE] Add swagger dependency to Ignite 3
Hello! Back when I looked at it, Swagger was very primitive, such as not supporting primitive types in generated models https://stackoverflow.com/a/45053804/36498 I'm not sure it is the right tool, please clarify why it is needed. -0.5 from me (binding) Regards, -- Ilya Kasnacheev пн, 23 мая 2022 г. в 19:57, Aleksandr Pakhomov : > Dear community, > > Discussion about 3rd party dependencies took place > and I think it is time to vote if we agreed to include > swagger dependency to the Ignite 3 or not. > > The exact list of dependencies could be fined in IEP-87 [1] > (swagger-annotations, swagger-core, > swagger-codegen-maven-plugin) > > Micronaut is out of the scope of this voting. I will launch > a separate one. > > The vote is formal, see voting guidelines [2] > > +1 - to accept additional dependencies to be included to Java code > Guidelines [3] > 0 - don't care either way > -1 - DO NOT accept (explain why) > > [1] > https://cwiki.apache.org/confluence/display/IGNITE/IEP-87%3A+Open+API+support+for+REST#IEP87:OpenAPIsupportforREST-Additionaldependencies > [2] https://www.apache.org/foundation/voting.html < > https://www.apache.org/foundation/voting.html> > [3] > https://cwiki.apache.org/confluence/display/IGNITE/Java+Code+Style+Guide#JavaCodeStyleGuide-2Using3rdpartylibraries
Re: restful api get key result is null,but java thin clien get key has result
Hello! Please write to user list (u...@ignite.apache.org) Having said that, I think you need to qualify this key class with package name when doing REST. Regards, -- Ilya Kasnacheev пн, 23 мая 2022 г. в 13:59, wkhapy...@163.com : > i use java thin client i > > > > wkhapy...@163.com >
Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions
Hello! Can you arrange that? Regards, -- Ilya Kasnacheev чт, 19 мая 2022 г. в 09:20, Maxim Muzafarov : > Ilya, > > Should we start a formal vote about the ignite-schedule deletion? > > On Mon, 16 May 2022 at 14:28, Ilya Kasnacheev > wrote: > > > > Hello! > > > > In my opinion, the ignite-schedule module needs to be dropped - it has > bad > > API, outdated GPL dependency and in general is out of focus of Ignite. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пт, 13 мая 2022 г. в 17:51, Maxim Muzafarov : > > > > > Folks, > > > > > > I've found that the following modules are rarely used and haven't been > > > change for a few years, but they are released each time Ignite being > > > released. It seems we can safely move all of them to the Extensions > > > project. > > > > > > The list: > > > - ignite-yarn > > > - ignite-geospatial > > > - ignite-schedule > > > > > > WDYT? > > > >
Re: [DISCUSSION] Move the ignite-yarn, ignite-geospatial, ignite-schedule to the Ignite Extensions
Hello! In my opinion, the ignite-schedule module needs to be dropped - it has bad API, outdated GPL dependency and in general is out of focus of Ignite. Regards, -- Ilya Kasnacheev пт, 13 мая 2022 г. в 17:51, Maxim Muzafarov : > Folks, > > I've found that the following modules are rarely used and haven't been > change for a few years, but they are released each time Ignite being > released. It seems we can safely move all of them to the Extensions > project. > > The list: > - ignite-yarn > - ignite-geospatial > - ignite-schedule > > WDYT? >
Re: Contibutor permissions
Hello! You seem to already have Confluence access. Since 3 of your Jira usernames are the same, I suggest you to rename the right one so that I can identify and add it. Alternatively, you can rename old ones. E-mail is not visible to me. Regards, -- Ilya Kasnacheev пт, 6 мая 2022 г. в 21:41, Mikhail Pochatkin : > Hello, I would like to contribute to the Apache Ignite project. Could you > please add me to the Contributors group in JIRA and Confluence? > > Jira Username "Mikhail Pochatkin mpochat...@unison.team" > Confluence Username "mpochatkin mpochat...@unison.team" > > Thank you! >
Re: [VOTE] Release Apache Ignite 2.13.0 RC2
+1 (binding) Ran a slim node, built from sources, built and ran c++ node. Regards, -- Ilya Kasnacheev пн, 25 апр. 2022 г. в 08:55, Николай Ижиков : > +1 (binding) > > > 23 апр. 2022 г., в 17:32, Nikita Amelchev > написал(а): > > > > Hi Igniters, PMCs, > > > > Please, verify a new release candidate. > > > > The vote will continue until there are enough votes for a resolution. [1] > > > > [1] https://www.apache.org/foundation/voting.html#ReleaseVotes > > > > пт, 22 апр. 2022 г. в 08:24, Zhenya Stanilovsky > : > >> > >> > >> Nikita thanks for your effort ! > >> Download sources, run examples. > >> +1 from me. > >> > >>> Dear Community, > >>> > >>> The release candidate is ready. > >>> > >>> I have uploaded a release candidate to: > >>> https://dist.apache.org/repos/dist/dev/ignite/2.13.0-rc2/ > >>> https://dist.apache.org/repos/dist/dev/ignite/packages_2.13.0-rc2/ > >>> > >>> The following staging can be used for testing: > >>> > https://repository.apache.org/content/repositories/orgapacheignite-1542 > >>> > >>> Tag name is 2.13.0-rc1: > >>> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=refs/tags/2.13.0-rc2 > >>> > >>> RELEASE_NOTES: > >>> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.13 > >>> > >>> Complete list of resolved issues: > >>> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.13%27))%20and%20status%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority > >>> > >>> DEVNOTES: > >>> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.13 > >>> > >>> Additional checks have been performed (available for users included > >>> into the release group on TeamCity). > >>> > >>> TC [Check RC: Licenses, compile, chksum] > >>> > https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum/6399934 > >>> > >>> TC [2] Compare w/ Previous Release > >>> > https://ci2.ignite.apache.org/buildConfiguration/ignite2_Release_ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6399932 > >>> > >>> The vote is formal, see voting guidelines > >>> https://www.apache.org/foundation/voting.html > >>> > >>> +1 - to accept Apache Ignite 2.13.0-rc2 > >>> 0 - don't care either way > >>> -1 - DO NOT accept Apache Ignite Ignite 2.13.0-rc2 (explain why) > >>> > >>> See notes on how to verify release here > >>> https://www.apache.org/info/verification.html > >>> and > >>> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification > >>> > >>> This vote will be open for at least 3 days till Fri Apr 23, 2022, > >>> 20:00 UTC. Please, write me down the thread if you need additional > >>> time to check the > >>> release. > >>> > https://www.timeanddate.com/countdown/vote?iso=20220423T20=0=VOTE+on+the+Apache+Ignite+Release+2.13.0+RC2=sanserif > >>> > >>> -- > >>> Best wishes, > >>> Amelchev Nikita > >> > >> > >> > >> > > > > > > > > -- > > Best wishes, > > Amelchev Nikita > >
Re: Hello
Hello! I have added you to Contributors role, you may now assign issues to yourself. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 12 апр. 2022 г. в 07:48, Benjamin Mankowitz : > Hello Ignite Community! > > My name is Benjamin Mankowitz. I want to contribute to Apache Ignite and > want to start with this issue - IGNITE-16465, my JIRA username is > bmankowitz. Any help on this will be appreciated, especially if anyone > knows how to reproduce the bug. > > Thanks! >
Re: [DISCUSSION] Remove scalar module
Hello! I think it is a good idea, it takes ages to compile and I assume the Scala version we use is really outdated now. Regards, -- Ilya Kasnacheev чт, 7 апр. 2022 г. в 14:07, Николай Ижиков : > Hello, Igniters. > > Looks like scalar module abandoned for at least for 4 years - no user-list > questions, no source updates. > I propose to remove it completely. > > WDYT?
Re: Reg: Looking for Ignite index H2 version Updating solution
Hello! Later version of H2 removed some of APIs which Ignite is using so we can't use those. We plan to get rid of H2 eventually, when we move to Calcite. Regards, -- Ilya Kasnacheev ср, 16 мар. 2022 г. в 19:30, sameiksha kiran k : > Hai Team , > > Ignite indexing is using lower version of H2 version which is issue to > other dependencies in my application ,even the latest release of ignite is > using lower version of H2 , excluding h2 and adding explicitly add H2 > version is not possible > > Is there any reason H2 version is not getting upgraded in ignite or Please > let me know if any chances or ways to upgrade H2 version > > Thanks a lot in advance > > > Regards, > Sameiksha >
Re: [jira] [Created] (IGNITE-16617) Delete the sections related to FIRSTVALUE and LASTVALUE functions in the document
Hello! I have pushed the change to master, thank you for looking into this. Regards, -- Ilya Kasnacheev вт, 22 февр. 2022 г. в 14:39, 18624049226 <18624049...@163.com>: > Is there anyone willing to help merge the following PR? > > https://github.com/apache/ignite/pull/9845 > > 在 2022/2/22 18:57, YuJue Li (Jira) 写道: > > YuJue Li created IGNITE-16617: > > - > > > > Summary: Delete the sections related to FIRSTVALUE and > LASTVALUE functions in the document > > Key: IGNITE-16617 > > URL:https://issues.apache.org/jira/browse/IGNITE-16617 > > Project: Ignite > >Issue Type: Improvement > >Components: documentation > > Affects Versions: 2.12 > > Reporter: YuJue Li > > Fix For: 2.13 > > > > > > [https://ignite.apache.org/docs/latest/sql-reference/aggregate-functions > ] > > > > Ignite does not support these two functions, so community should delete > the related contents from the document. > > > > > > > > -- > > This message was sent by Atlassian Jira > > (v8.20.1#820001)
Re: Nabble forum scheduled for deletion
Hello! It would be a pity if they delete that, but I can't see any instructions there. Regards, -- Ilya Kasnacheev вт, 25 янв. 2022 г. в 18:22, Nabble : > > Dear Nabble user, > > The forum listed below is inactive and has been scheduled for deletion in > 30 days. > To prevent this forum from being deleted, visit the forum and follow the > instructions. > > http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/ > > If this forum is deleted, your posts in this forum will be deleted. > You can see your posts here: > > > http://apache-ignite-developers-legacy-mail-archive.111.s1.nabble.com/template/NamlServlet.jtp?macro=user_nodes=1 > > ** For more information, see: > http://s1.nabble.com/help/Answer.jtp?id=53 > > Regards, > The Nabble team >
Re: A new feedback has been added : 52
Hello! We no longer advertise SQL transactions so it's only logical. Regards, -- Ilya Kasnacheev чт, 13 янв. 2022 г. в 20:28, Bugyard : > A new feedback has been added, go to bugyard.io to see all the details... > > https://bugyard.io > > A new feedback has been added > > "There is bug in 2.11.1 ignite documentation: link > https://ignite.apache.org/docs/latest/SQL/sql-transactions lead to wrong > page (introduction)" by erakhmanulov > > View feedback > https://app.bugyard.io/web/app/rycqZJDyY/f/61e05efc38569600142ffc65
Re: A new feedback has been added : 50
Indeed https://ignite.apache.org/releases/latest/dotnetdoc/ won't open. -- Ilya Kasnacheev пн, 10 янв. 2022 г. в 05:22, Bugyard : > A new feedback has been added, go to bugyard.io to see all the details... > > https://bugyard.io > > A new feedback has been added > > "You .NET API Document has been generating a 404 for some time now from > the menu. Browsing the directory, it seems to be missing. It thought it > would ultimately be fixed, but it seems not. It use to be available. I > would but appreciate having access. Thanks you in advance." by > louis.fournier > > View feedback > https://app.bugyard.io/web/app/rycqZJDyY/f/61db9235b6a71d0014891b7e
Re: Move the Zookeeper IP-finder to the ignite-extensions
Hello! OK, I'm retracting my claim then. IP-finder may indeed be moved to extensions. Regards, -- Ilya Kasnacheev ср, 22 дек. 2021 г. в 14:00, Ivan Daschinsky : > >> a lot of code in core code base is dedicated for enabling it. > It is simply not true. ZookeeperDiscovery has nothing common with > ZookeeperIpFinder. > > The last one is simply one class and similar to others IP finders. > > ср, 22 дек. 2021 г. в 13:25, Ilya Kasnacheev : > > > Hello! > > > > I think it might not be a good idea, since Zookeeper IP Finder is not > > stand-alone - a lot of code in core code base is dedicated for enabling > it. > > This code may break unnoticed if Zookeeper IP Finder is not built/tested > on > > every commit. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > ср, 22 дек. 2021 г. в 12:09, Sergei Ryzhov : > > > > > Hi, igniters, > > > > > > I've created an issue [1] to move the zookeeper IP-finder to the > > > ignite-extensions. The motivation is the same as with migration of > > > cloud-based IP-finders - to remove integration dependency of the > > > release cycle on Ignite releases. Also, the log4j dependency with > > > vulnerabilities (needed for Apache Curator) will be removed from the > > Ignite > > > release. > > > > > > Any objections? > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-16182 > > > -- > > > Best regards, > > > Sergei Ryzhov > > > > > > > > -- > Sincerely yours, Ivan Daschinskiy >
Re: [RESULT] [VOTE] Release Apache Ignite 2.11.1 RC2
Hello! Downloads page does not seem to have correct release date for releases older than 2.11. Can this be fixed? Regards, -- Ilya Kasnacheev вт, 21 дек. 2021 г. в 14:47, Denis Magda : > Hi Maxim, > > Just a reminder that since the release of the new website, we need to > update the download.pug [1] file in case of a release and then generate the > HTML version following this updated instruction. If you have any questions, > please reach out to Erlan (CC-ed). > > [1] https://github.com/apache/ignite-website/blob/master/_src/download.pug > [2] https://cwiki.apache.org/confluence/display/IGNITE/Website+Development > > On Tue, Dec 21, 2021 at 4:36 AM Maxim Muzafarov wrote: > > > Hello, Igniters! > > > > > > Thanks to everyone. The vote is closed. > > The emergency Apache Ignite 2.11.1 release (RC2) has been accepted. > > I will continue on with the release. > > > > 5 - "+1" votes received and no "0", "-1" votes. > > > > > > Here are the votes received: > > > > - Ilya Kasnacheev (binding) > > - Pavel Tupitsyn (binding) > > - Ivan Daschinsky > > - Nikolay Izhikov (binding) > > - Vyacheslav Koptilin > > - Alex Plehanov (binding) > > - Valentin Kulichenko (binding) > > > > > > Here is the link to the voting thread: > > https://lists.apache.org/thread/2pwc0fv0pczhnxbyfkdhl1m3yvh8vrpb > > > > Thank you! > > >
Re: Move the Zookeeper IP-finder to the ignite-extensions
Hello! I think it might not be a good idea, since Zookeeper IP Finder is not stand-alone - a lot of code in core code base is dedicated for enabling it. This code may break unnoticed if Zookeeper IP Finder is not built/tested on every commit. Regards, -- Ilya Kasnacheev ср, 22 дек. 2021 г. в 12:09, Sergei Ryzhov : > Hi, igniters, > > I've created an issue [1] to move the zookeeper IP-finder to the > ignite-extensions. The motivation is the same as with migration of > cloud-based IP-finders - to remove integration dependency of the > release cycle on Ignite releases. Also, the log4j dependency with > vulnerabilities (needed for Apache Curator) will be removed from the Ignite > release. > > Any objections? > > [1] https://issues.apache.org/jira/browse/IGNITE-16182 > -- > Best regards, > Sergei Ryzhov >
Re: [VOTE] Release Apache Ignite 2.11.1 RC2
Hello! +1 There seems to be a correct version of log4j2 now. Btw, I've noticed that we ship log2j 1.x with ignite-rest-http. This is quite bad. Regards, -- Ilya Kasnacheev пн, 20 дек. 2021 г. в 15:35, Maxim Muzafarov : > The second release candidate for the 2.11.1 version is ready. > > Since this is an emergency release the vote will remain open for as > short an amount as time as required to vet the release. All votes are > welcome and we encourage everyone to test the release, but only PMC > votes are “officially” counted. As always, at least 3 +1 votes and > more positive than negative votes are required. See voting guidelines: > https://www.apache.org/foundation/voting.html > > +1 - to accept Apache Ignite 2.11.1-rc2 > 0 - don't care either way > -1 - DO NOT accept Apache Ignite Ignite 2.11.1-rc2 (explain why) > > > * RELEASE CANDADATE * > > Check the release difference between 2.11 and 2.11.1: > https://github.com/apache/ignite/compare/ignite-2.11...ignite-2.11.1 > > I have uploaded a release candidate to: > https://dist.apache.org/repos/dist/dev/ignite/2.11.1-rc2/ > https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.1-rc2/ > > The following staging can be used for testing: > https://repository.apache.org/content/repositories/orgapacheignite-1535/ > > https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite > > The tag name is 2.11.1-rc2: > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=eae1147dd1cd625cc229098489be8d208f6cabcc > > RELEASE_NOTES: > > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11.1 > > Complete list of resolved issues: > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.11.1%27)) > > > * CHECKS * > > Additional checks have been performed (available for users included into > the release group on TeamCity). > > TC [Check RC: Licenses, compile, chksum] > > https://ci.ignite.apache.org/viewLog.html?buildId=6333527=ApacheIgniteReleaseJava8_PrepareVote3BuildNuGetPackages > > See notes on how to verify release here > https://www.apache.org/info/verification.html > and > > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification >
Re: Apache Ignite 2.11.1 RELEASE [Time, Scope, Manager]
Hello! I also agree with Stephen. If we wanted to do a stabilization release we should unbound it from this urgent fix. I wonder why 2.12 is not with us already, given that it was scheduled to go out in August. Regards, -- Ilya Kasnacheev чт, 16 дек. 2021 г. в 19:25, Вячеслав Коптилин : > Hello, > > > Given that 2.12 is so close, my preference would be to limit the scope of > 2.11.1 to just the log4j update. > I agree with Stephen. Apache Ignite 2.11.1 is an emergency release. Using > log4j 2.16 instead of 2.14 is a quite small change that only requires a > "sanity" check and can be quickly released. A wider release scope requires > full testing, IMHO. > > Thanks, > S. > > > чт, 16 дек. 2021 г. в 16:03, Maxim Muzafarov : > > > I think it is completely possible to move vote/release dates > > significantly forward with keeping the scope. I will take a look at > > the list of fixed bugs more narrowly and exclude some of them that > > require additional verification. > > > > On Thu, 16 Dec 2021 at 15:55, Stephen Darlington > > wrote: > > > > > > Given that 2.12 is so close, my preference would be to limit the scope > > of 2.11.1 to just the log4j update. Would that help bring the > vote/release > > date forward? > > > > > > > On 16 Dec 2021, at 12:44, Maxim Muzafarov wrote: > > > > > > > > Dear Ignite Community! > > > > > > > > I suggest preparing the Apache Ignite 2.11.1 release and I want to > > > > propose myself to be the release manager of the minor release. > > > > > > > > > > > > * RELEASE TIMELINE * > > > > > > > > Scope Freeze: December 16, 2021 > > > > Code Freeze: December 16, 2021 > > > > Voting Date: December 21, 2021 > > > > Release Date: December 24, 2021 > > > > > > > > > > > > * RELEASE SCOPE * > > > > > > > > LOG4J dependency update > > > > https://issues.apache.org/jira/browse/IGNITE-16101 > > > > https://issues.apache.org/jira/browse/IGNITE-16127 > > > > > > > > B+Tree Corrupted exception when using a key extracted from a > > BinaryObject > > > > https://issues.apache.org/jira/browse/IGNITE-12911 > > > > > > > > Regression: Ignite node crash(CorruptedTreeException: B+Tree is > > corrupted) > > > > https://issues.apache.org/jira/browse/IGNITE-15943 > > > > > > > > .NET: ClientFailoverSocket sets logger too late, resulting in null > > > > loggers downstream > > > > https://issues.apache.org/jira/browse/IGNITE-14776 > > > > > > > > The iterator of the ClientCacheQueryCursor can be closed during > > serialization. > > > > https://issues.apache.org/jira/browse/IGNITE-15346 > > > > > > > > Possible owners desync when a node is restarted while rebalancing > with > > > > enabled persistence > > > > https://issues.apache.org/jira/browse/IGNITE-15315 > > > > > > > > Thin client: Tx can fail if there are concurrent tx rollbacks by > > timeout > > > > https://issues.apache.org/jira/browse/IGNITE-15732 > > > > > > > > AssertionError: Unexpected rebalance on rebalanced cluster > > > > https://issues.apache.org/jira/browse/IGNITE-15033 > > > > > > > > JmxMetricExporterSpi throws assertion error on a filtered metric > > unregister > > > > https://issues.apache.org/jira/browse/IGNITE-15252 > > > > > > > > ClassNotFoundException on an attempt to invoke service method from > > > > Java ThinClient after a cluster failover > > > > https://issues.apache.org/jira/browse/IGNITE-15256 > > > > > > > > NullPointerException on an attempt to create a Java ThinClient with > > > > BinaryConfiguration > > > > https://issues.apache.org/jira/browse/IGNITE-15138 > > > > > > > > Java thin client: Type name is not cached on client-side for > > > > OptimizerMarshaller types > > > > https://issues.apache.org/jira/browse/IGNITE-15924 > > > > > > > > select count * returns multiple rows > > > > https://issues.apache.org/jira/browse/IGNITE-14120 > > > > > > > > Fix StackOverflowError in case if an exception is suppressed with > > itself > > > > https://issues.apache.org/jira/browse/IGNITE-15716 > > > > > > > > > > > > WDYT? > > > > > > > > >
Re: [DISCUSSION] Reject join of nodes with different character encodings
Hello! We already have a warning about this, see IgniteKernal.checkFileEncoding() Regards, -- Ilya Kasnacheev пн, 13 дек. 2021 г. в 16:26, Ivan Daschinsky : > >> But now multiple components > >> independently serialize strings for their needs and use default encoding > >> for this. > >> For example DirectByteBufferStreamImplV2#writeString, > >> MetaStorage#writeRaw and so on > We should fix all of them. > > >> BinaryUtils#utf8BytesToStr > Lets use this everywhere. > > As for me, I'm expecting a way more problem with enforcing rule to fail, > rather than enforcing all components to use UTF-8 > Some weird cases (surrogate pairs) we can (I strongly believe it is OK) > simply do not consider at all. > > пн, 13 дек. 2021 г. в 15:15, Nikolay Izhikov : > > > > Does Java String support all unicode characters and particularly does > it > > support more characters than UTF-8 > > > > It’s not about Java, it’s about UTF-8 standard. > > > > Please, take a look at [1] > > > > > In November 2003, UTF-8 was restricted by RFC 3629 to match the > > constraints of the UTF-16 character encoding: explicitly prohibiting code > > points corresponding to the high and low surrogate characters removed > more > > than 3% of the three-byte sequences, and ending at U+10 removed more > > than 48% of the four-byte sequences and all five- and six-byte sequences. > > > > And [2] > > > > > The definition of UTF-8 prohibits encoding character numbers between > > U+D800 and U+DFFF, which are reserved for use with the UTF-16 encoding > form > > (as surrogate pairs) and do not directly represent characters. > > > > Actually, we already has some modes to support this restriction of UTF-8. > > Please, take a look at BinaryUtils#utf8BytesToStr [3] > > > > > > [1] https://en.wikipedia.org/wiki/UTF-8 > > [2] https://datatracker.ietf.org/doc/html/rfc3629 > > [3] > > > https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/binary/BinaryUtils.java#L2387 > > > > > 13 дек. 2021 г., в 13:57, Ivan Pavlukhin > > написал(а): > > > > > >> UTF-8 can’t encode all UNICODE characters. > > > > > > Nikolay, could you please elaborate? My understanding is that encoding > > > we speak about matters for conversion from byte arrays to strings. > > > Does Java String support all unicode characters and particularly does > > > it support more characters than UTF-8 (I am not saying here that java > > > String uses UTF-8)? > > > > > > 2021-12-13 12:56 GMT+03:00, Ivan Daschinsky : > > >> UTF-8 is already a default encoding in our BinaryObject format. So > > I am > > >> for unification. > > >> > > >> пн, 13 дек. 2021 г. в 12:50, Nikolay Izhikov : > > >> > > >>> Hello, Ivan. > > >>> > > >>> UTF-8 can’t encode all UNICODE characters. > > >>> > > >>>> 13 дек. 2021 г., в 12:49, Ivan Daschinsky > > >>> написал(а): > > >>>> > > >>>> Khm, maybe a better variant is to enforce all strings to be encoded > > in > > >>>> UTF-8? > > >>>> AFAIK multi OS cluster is a quite common case. > > >>>> > > >>>> > > >>>> пн, 13 дек. 2021 г. в 11:36, Mikhail Petrov >: > > >>>> > > >>>>> Igniters, > > >>>>> > > >>>>> Recently we faced the problem that if the cluster consists of nodes > > >>>>> running in the JVM with different encodings, many issues arise. > > >>>>> The root cause of the mentioned issues is components that use > > >>>>> `String#getBytes()` and `new String()`, which relies on > > >>>>> the > > >>>>> system default encoding. Thus, if a string is deserialized on a > node > > >>>>> with a different encoding from the one that serialized it, the > > >>>>> deserialized string can be different from the original one. > > >>>>> > > >>>>> For example: > > >>>>> > > >>>>> Serialization/deserialization of string in communication messages > may > > >>>>> be > > >>>>> broken for some strings on nodes running in a JVM with a different > > >>>>> encoding as DirectByteBufferStreamImplV2 uses String#getBytes() to > > >>>>> serialize strings - [1] > > >>>>> > > >>>>> Or the IgniteAuthenticationProcessor can compute different security > > >>>>> IDs > > >>>>> for the user on different nodes in this case - [2] > > >>>>> > > >>>>> What do you think, if we solve this problem globally, by rejecting > to > > >>>>> join nodes that run on JVMs with different encodings? > > >>>>> > > >>>>> As a result, we will be sure that all cluster nodes have the same > > >>>>> encoding and all related problems will be solved. > > >>>>> > > >>>>> [1] - https://issues.apache.org/jira/browse/IGNITE-16106 > > >>>>> [2] - https://issues.apache.org/jira/browse/IGNITE-16068 > > >>>>> > > >>>>> -- > > >>>>> Mikhail > > >>>>> > > >>>>> > > >>>> > > >>>> -- > > >>>> Sincerely yours, Ivan Daschinskiy > > >>> > > >>> > > >> > > >> -- > > >> Sincerely yours, Ivan Daschinskiy > > >> > > > > > > > > > -- > > > > > > Best regards, > > > Ivan Pavlukhin > > > > > > -- > Sincerely yours, Ivan Daschinskiy >
Re: Re[2]: NUMA aware allocator, PR review request
Hello! Maybe I am wrong, but ODBC installer is built from source and may be improved from release to release. Regards, -- Ilya Kasnacheev пн, 6 дек. 2021 г. в 20:41, Ivan Daschinsky : > Only one reason -- nowadays amost all hardware platforms uses NUMA > > Another reason -- there is no any release process of extensions. > > > BTW, apache ignite release is shipped with odbc binary installer for > windows. And nobody complains about it. > > But may be listen to others? > > пн, 6 дек. 2021 г., 19:49 Anton Vinogradov : > > > Any reason to release the same cpp sources for each release? > > Any reason to increase the requirements amount for each new release? > > Any reason to increase release complexity and duration? > > All answers are "definitely no" > > > > What we should do is to release cpp part once and use it as a dependency. > > Extensions are a good location. > > > > On Mon, Dec 6, 2021 at 3:11 PM Zhenya Stanilovsky > > wrote: > > > > > > > > > > > +1 with Ivan, let`s store it in core product just because it looks > > > like inalienable functionality and release cycle of extensions a little > > bit > > > different. > > > > > > > > > > > > >Anton, I disagree. > > > > > > > >1. This should be released with main distro. > > > >2. This should not be abandoned. > > > >3. There is not any release process in ignite-extensions. > > > >4. Everything is working now and working good. > > > > > > > > > > > >So lets do not do this :) > > > > > > > >пн, 6 дек. 2021 г. в 14:49, Anton Vinogradov < a...@apache.org >: > > > > > > > >> Let's move all GCC-related parts to ignite-extensions, release, and > > use > > > >> them as a maven dependency. > > > >> > > > >> > > > >> On Fri, Dec 3, 2021 at 1:08 PM Ivan Daschinsky < > ivanda...@gmail.com > > > > > > >> wrote: > > > >> > > > >> > Ok, TC suite is ready [1]. > > > >> > If there is no objections, I will merge it soon. > > > >> > > > > >> > Possible concerns -- now it is required to install > build-essentials > > > and > > > >> > libnuma-dev in order to build ignite on 64 bit linux. > > > >> > I suppose that this is not a big deal, but maybe someone will > > > contradict? > > > >> > > > > >> > > > > >> > [1] -- > > > >> > > > > >> > > > > >> > > > > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_NumaAllocator/?mode=builds > > > >> > > > > >> > чт, 2 дек. 2021 г. в 12:03, Ivan Daschinsky < ivanda...@gmail.com > > >: > > > >> > > > > >> > > >> Our runs show about 7-10 speedup, > > > >> > > Sorry, typo 7-10% speedup > > > >> > > > > > >> > > чт, 2 дек. 2021 г. в 12:01, Ivan Daschinsky < > ivanda...@gmail.com > > > >: > > > >> > > > > > >> > >> Andrey, thanks! > > > >> > >> > > > >> > >> This allocator can be tested on every NUMA system. > > > >> > >> Our runs show about 7-10 speedup, if we use allocattor with > > > >> interleaved > > > >> > >> strategy + -XX:+UseNUMA. > > > >> > >> But unfortunately our yardstick benches doesn't use offheap a > > lot, > > > >> > >> usually above one Gb. > > > >> > >> We trying to do more benches with real data and share them, > > > possibly > > > >> in > > > >> > >> meetup. > > > >> > >> > > > >> > >> AFAIK, GG lab servers are two-sockets machines, aren't they? So > > it > > > is > > > >> > >> worth to run benches with a lot data on them, using > > > >> > >> allocator with interleaved strategy (you can skip specifying > numa > > > >> nodes, > > > >> > >> by default it will use all available) and use -XX:+UseNUMA jvm > > > >> > >> flag. > > > >> > >> > > > >> > >> > > > >> > >> > > > >> > >>
Re: Join contributors
Hello! I have added you to the Contributors role. You may now assign issues to yourself. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 16 нояб. 2021 г. в 22:12, Dmitriy Borunov : > Hello Ignite community! > > My name is Dmitriy Borunov. I would like to contribute to Apache > Ignite. My Apache JIRA username is dmitriy.borunov. > Could you please provide me with the corresponding permission? >
Re: Stop sending IGNITE Created e-mails to dev@
Hello! I have raised https://issues.apache.org/jira/browse/INFRA-22520 Regards, -- Ilya Kasnacheev пт, 12 нояб. 2021 г. в 11:49, Вячеслав Коптилин : > Hello, > > Yep, absolutely the same. > > Thanks, > S. > > > пт, 12 нояб. 2021 г. в 11:12, Ivan Pavlukhin : > > > A last one I received was IGNITE-15872 as well. > > > > 2021-11-11 22:43 GMT+03:00, Ilya Kasnacheev : > > > Hello! > > > > > > For some reason, looks like it has stopped working. I did not get any > > > notification for issues since IGNITE-15872. > > > > > > Is it just me? The settings in the JIRA seem alright. > > > > > > Regards, > > > > > > сб, 1 мая 2021 г. в 12:49, Mikhail Petrov : > > > > > >> It works. Thanks a lot! > > >> > > >> Sent from my iPhone > > >> > > >> On 30 Apr 2021, at 15:20, Ilya Kasnacheev > > >> wrote: > > >> > > >> > > >> Hello! > > >> > > >> I have added you to this role > > >> > > >> Regards, > > >> -- > > >> Ilya Kasnacheev > > >> > > >> > > >> пт, 30 апр. 2021 г. в 11:55, Mikhail Petrov : > > >> > > >>> Hi, Ilya, could you please add me to "Contributors 1" role? Or can I > do > > >>> it myself somehow? > > >>> > > >>> On 29.04.2021 18:59, Ilya Kasnacheev wrote: > > >>> > > >>> Hello! > > >>> > > >>> Pavel, Yurii, I have added you both to the role. > > >>> > > >>> Regards, > > >>> > > >>> > > > > > > > > > -- > > > > Best regards, > > Ivan Pavlukhin > > >
Re: Stop sending IGNITE Created e-mails to dev@
Hello! For some reason, looks like it has stopped working. I did not get any notification for issues since IGNITE-15872. Is it just me? The settings in the JIRA seem alright. Regards, сб, 1 мая 2021 г. в 12:49, Mikhail Petrov : > It works. Thanks a lot! > > Sent from my iPhone > > On 30 Apr 2021, at 15:20, Ilya Kasnacheev > wrote: > > > Hello! > > I have added you to this role > > Regards, > -- > Ilya Kasnacheev > > > пт, 30 апр. 2021 г. в 11:55, Mikhail Petrov : > >> Hi, Ilya, could you please add me to "Contributors 1" role? Or can I do it >> myself somehow? >> >> On 29.04.2021 18:59, Ilya Kasnacheev wrote: >> >> Hello! >> >> Pavel, Yurii, I have added you both to the role. >> >> Regards, >> >>
Re: [VOTE][EXTENSION] Release Apache Ignite spring-tx-ext, spring-cache-ext extensions 1.0.0 RC1
Hello! I think we should write in documentation that the module is only suitable for AI 2.13 or later. And then in AI 2.13 we remove these classes from ignite-spring. It does not make sense to use this module before AI 2.13. It may be possible but does not have any practical purpose. Regards, -- Ilya Kasnacheev вс, 31 окт. 2021 г. в 13:46, Mikhail Petrov : > Ilya, for Ignite 2.10 versions and earlier spring-tx and spring-cache > integrations are stored in the ignite-spring module. Initially, there > were no dedicated modules for them. As I see, we cannot fully migrate > the ignite-spring module as it is responsible for parsing Ignite XML > configurations and included in binary release. Therefore, if the users > want to use the mentioned above extensions with Ignite 2.10 or earlier > they can get two copies of the Ignite extension classes in their > classpath - one from extension dependency and one from ignite-spring. > This problem cannot be solved by excluding some modules - only by > shading or specifying some classes before others in the classpath. > > WDYT? > > > -- > Mikhail > > > On 31.10.2021 01:13, Ilya Kasnacheev wrote: > > Hello! > > > > + 0.5 > > > >> Apache Ignite 2.10.0 and earlier the ignite-spring-cache-ext dependency > > must be added to classpath before ignite-spring, due to duplication of > > Spring Cache integration classes. > > > > I think this recommendation does not have much sense - the order of > > classpath and maven dependency resolution is not something you may count > > on. We could teach our users to do proper maven exclusion instead (what > is > > the module which they need to exclude - is it spring-cache? which classes > > are duplicated?) > > > > But otherwise maybe we should get it out of door and finish the > migration. > > > > Regards, >
Re: [VOTE][EXTENSION] Release Apache Ignite spring-tx-ext, spring-cache-ext extensions 1.0.0 RC1
Hello! + 0.5 > Apache Ignite 2.10.0 and earlier the ignite-spring-cache-ext dependency must be added to classpath before ignite-spring, due to duplication of Spring Cache integration classes. I think this recommendation does not have much sense - the order of classpath and maven dependency resolution is not something you may count on. We could teach our users to do proper maven exclusion instead (what is the module which they need to exclude - is it spring-cache? which classes are duplicated?) But otherwise maybe we should get it out of door and finish the migration. Regards, -- Ilya Kasnacheev ср, 27 окт. 2021 г. в 11:48, Nikita Amelchev : > Dear Ignite Community, > > I have uploaded a release candidate of extensions modules: > - spring-tx-ext 1.0.0 > - spring-cache-ext 1.0.0 > - spring-data-commons 1.1.0 > > The following staging can be used for testing: > https://repository.apache.org/content/repositories/orgapacheignite-1533 > > The release candidate of the spring-tx-ext 1.0.0 extension: > > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-tx-ext/1.0.0-rc1/ > > The release candidate of the spring-cache-ext 1.0.0 extension: > > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-cache-ext/1.0.0-rc1/ > > The release candidate of the spring-data-common 1.1.0 dependent module > is in the packages mentioned above. > > Tags were created: > ignite-spring-tx-ext-1.0.0-rc1 > ignite-spring-cache-ext-1.0.0-rc1 > ignite-spring-data-commons-1.1.0-rc1 > > > https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=refs/tags/ignite-spring-tx-ext-1.0.0-rc1 > > RELEASE NOTES: > > https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=c6b2a393e042ce956bfefd5d7d92d5ab4ff04cda;hb=HEAD > > DOCUMENTATION: > Documentation of the spring-tx-ext extension: > > https://github.com/apache/ignite/blob/master/docs/_docs/extensions-and-integrations/spring/spring-tx.adoc > > Documentation of the spring-cache-ext extension: > > https://github.com/apache/ignite/blob/master/docs/_docs/extensions-and-integrations/spring/spring-caching.adoc > > The vote is formal, see voting guidelines > https://www.apache.org/foundation/voting.html > > +1 - to accept the extensions modules listed in the thread > 0 - don't care either way > -1 - DO NOT accept either of the extensions modules listed in the > thread (explain why) > > The vote will hold for 5 days and will end on November 1, 2021, 10:00 UTC > https://www.timeanddate.com/countdown/generic?iso=20211101T10=0 > > -- > Best wishes, > Amelchev Nikita >
Re: Apache Ignite 2.12 RELEASE [Time, Scope, Manager]
Hello! I have prepared a fix for sqlline.sh -e: https://github.com/apache/ignite/pull/9536 If smbd reviews it, we can put it on 2.12. Regards, -- Ilya Kasnacheev чт, 28 окт. 2021 г. в 10:39, Nikita Amelchev : > Maksim, ok. > > Ivan, > The minor issues can be considered if they will be merged before the > code freeze. > > ср, 27 окт. 2021 г. в 14:55, Pavel Tupitsyn : > > > > Ivan, every additional ticket potentially moves the release date further. > > Also, AFAIK, Igor is on vacation and can't do a review this week. > > > > On Wed, Oct 27, 2021 at 2:32 PM Ivan Daschinsky > wrote: > > > > > Pavel, but what is the problem to include a minor refactoring? > Especially > > > before code freeze? > > > > > > ср, 27 окт. 2021 г. в 14:25, Pavel Tupitsyn : > > > > > > > Ivan, IGNITE-15806 seems to be a minor refactoring, not sure we > should > > > > inflate the scope with this. > > > > > > > > On Wed, Oct 27, 2021 at 2:13 PM Ivan Daschinsky > > > > > wrote: > > > > > > > > > Nikita, can we add > https://issues.apache.org/jira/browse/IGNITE-15806 > > > > this > > > > > ticket for release? > > > > > > > > > > ср, 27 окт. 2021 г. в 13:40, Maksim Timonin < > timonin.ma...@gmail.com>: > > > > > > > > > > > Hi, > > > > > > > > > > > > I'd like to include the ticket in 2.12. There was a performance > > > issue, > > > > I > > > > > > spent some time trying to figure it out. I prepared some fixes > and I > > > am > > > > > > going to submit a patch this week. > > > > > > > > > > > > I think this issue is critical to include to 2.12 together with > basic > > > > > > IndexQuery functionality, because this ticket provides expected > > > > behavior > > > > > of > > > > > > querying indexes - sorted over all nodes results. > > > > > > > > > > > > - IGNITE-15530: IndexQuery has to use MergeSort reducer [1] > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15530 > > > > > > > > > > > > On Wed, Oct 27, 2021 at 1:23 PM Nikita Amelchev < > > > namelc...@apache.org> > > > > > > wrote: > > > > > > > > > > > > > Hello. > > > > > > > > > > > > > > Code freeze is planned for Friday, October 29. > > > > > > > > > > > > > > There are 40 unresolved issues [1] in the release scope. I > suggest > > > > > > > bumping up the fix version if they will not be resolved till > the > > > code > > > > > > > freeze. > > > > > > > > > > > > > > Please, feel free to write if some of them are critical to be > in > > > the > > > > > > 2.12. > > > > > > > > > > > > > > Also, please, pay attention to unresolved documentation > issues. [2] > > > > > > > > > > > > > > Sergey, Petr, thanks for helping with TC. > > > > > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27))%20AND%20(component%20is%20EMPTY%20OR%20component%20not%20in%20(documentation))%20%20and%20status%20not%20in%20(%27CLOSED%27%2C%20%27RESOLVED%27)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20 > > > > > > > > > > > > > > [2] > > > > > > > > > > > > > > > > > > > > > > > > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.12%27)%20AND%20status%20NOT%20IN%20(Resolved%2C%20Closed)%20AND%20component%20in%20(documentation)%20ORDER%20BY%20priority%20%20%20%20%20%20%20%20%20 > > > > > > > > > > > > > > вт, 26 окт. 2021 г. в 12:50, Petr Ivanov >: > > > > > > > > > > > > > > > > Thanks, Sergey. > > > > > > > > > > > > > > > > I've also reconfigured nightly builds for ignite-2.12 branch. > > > > > > > > > > > > > > > > > > > > > > > > > On 22 Oct 2021, at 17:32, Сергей Утцель > > > > wrote: > > > > > > > > > > > > > > > > > > I configured TC bot to 'ignite-2.12' instead of > 'ignite-2.11' > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > Best wishes, > > > > > > > Amelchev Nikita > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Sincerely yours, Ivan Daschinskiy > > > > > > > > > > > > > > > > > > -- > > > Sincerely yours, Ivan Daschinskiy > > > > > > > -- > Best wishes, > Amelchev Nikita >
Re: C# Thin Client Data Streamer issue
Hello! I have added you to Contributors role. Now you may assign ticket to yourself. Please submit pull request once you have it. Regards, -- Ilya Kasnacheev вт, 26 окт. 2021 г. в 00:15, Timotheus Preisinger < timotheus.preisin...@gmx.net>: > Hello! > > I am saying hi here! I have just created issue IGNITE-155820 ( > https://issues.apache.org/jira/browse/IGNITE-15820): Streaming from .NET > Thin Client does not create table entries. > > The issue includes a small sample project in net5 and a proposal for the > fix. I am now trying to follow the „How to Contribute“ ( > https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute#HowtoContribute-Workingonaticket > ). > > Regards, > > > Timotheus. > >
Re: Request for contributor permission
Hello, Roman! I have added you to the Contributors role, you may now assign issues to yourself. Please make sure to follow https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 19 окт. 2021 г. в 10:48, Roman Puchkovskiy : > Hello Ignite community! > > My name is Roman Puchkovskiy. I would like to contribute to Apache > Ignite. My Apache JIRA username is rpuch. > Could you please provide me with the corresponding permission? > > Roman Puchkovskiy >
Re: A new feedback has been added : 10
Hello! OK, it sounds good. I can see that these were already merged. Can you check if these tickets may be closed? Also, there's a new crop of "feedbacks" on the dev list. Thanks, -- Ilya Kasnacheev чт, 30 сент. 2021 г. в 01:59, Nikita Safonov : > Hi Ilya! > > Currently we respond to users via the Bugyard.io reply form, which does not > support putting others on CC. > Nevertheless all the conversations are saved in Bugyard and can be reached > by all the Igniters. > > Regarding our previous discussion: > > As I mentioned before, I'm taking the first shift of maintaining the doc > feedback. > But since I'm not a committer, I cannot merge the changes and port them to > the latest branch (and, as a result, to have them deployed on the website). > For instance, several issues (#4 > <https://issues.apache.org/jira/browse/IGNITE-15349>, #5 > <https://issues.apache.org/jira/browse/IGNITE-15459>, #6 > <https://issues.apache.org/jira/browse/IGNITE-15461>) were resolved a > quiet > time ago, but they haven't been ported to the latest Ignite branch yet. > > So can I kindly ask you to help me with this during the shift? > > With best regards, > Nikita > > > > > > > > чт, 23 сент. 2021 г. в 11:21, Ilya Kasnacheev : > > > Hello! > > > > If we reply to users with emails, I suggest putting dev@ on CC. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > чт, 23 сент. 2021 г. в 03:54, Nikita Safonov >: > > > > > Hi Ilya! > > > > > > That’s a good point. I’d like to highlight that Ignite Doc Feedback > > service > > > credentials are stored here > > > < > https://cwiki.apache.org/confluence/display/IGNITE/Ignite+PMC+Resources > > >, > > > so anyone can see the user’s feedback on bugyard.io. As for now, only > me > > > and Igor Gusev are managing this. > > > But I do believe that 3 months (or any other period) shifts can be > > useful, > > > as well as periodic reports. > > > > > > By the way, we do reply to the users’ feedback with emails. What is > more, > > > the work on the feedback can be tracked via Apache Ignite Jira tickets. > > > Every doc feedback ticket’s title starts with «Bugyard feedback #...». > > > > > > I guess that I’m ready to take this role and to discuss the volunteers > > for > > > the upcoming shifts later. > > > > > > With best regards, > > > Nikita > > > > > > вт, 21 сент. 2021 г. в 21:56, Ilya Kasnacheev < > ilya.kasnach...@gmail.com > > >: > > > > > > > Hello! > > > > > > > > Dear developers, I suggest we should have someone responsible for > > > handling > > > > bugyard reports and writing about that on developers list. > > > > > > > > Feedback is hidden behind login and I have no idea what's there, much > > > less > > > > if it was fixed. > > > > > > > > I think we should have a reply to every Bugyard e-mail and maybe > > > > three-month long shifts of people responsible for that. Anybody > wishing > > > to > > > > take this role? > > > > > > > > Regards, > > > > -- > > > > Ilya Kasnacheev > > > > > > > > > > > > пн, 20 сент. 2021 г. в 17:10, Bugyard : > > > > > > > > > A new feedback has been added, go to bugyard.io to see all the > > > > details... > > > > > > > > > > https://bugyard.io > > > > > > > > > > A new feedback has been added > > > > > > > > > > "Looks like [Running Ignite with Java 11 or later] link is > broken." > > > by > > > > > tim239 > > > > > > > > > > View feedback > > > > > > https://app.bugyard.io/web/app/rycqZJDyY/f/61488444507c91001448c81c > > > > > > > > > >
Re: [DISCUSSION] Separate Jira project and Confluence space for Ignite 3
Hello! If we go the second route, we can call the field "Generation". Generation: Ignite 2.x Generation: Ignite 3 (no new tickets should ever be filed for Ignite 1.x but if they are, they should go to the first Generation) Regards. -- Ilya Kasnacheev ср, 29 сент. 2021 г. в 00:33, Valentin Kulichenko < valentin.kuliche...@gmail.com>: > As for the original topic, we need to come to a solution. Let me summarize > what we've discussed so far. > > -PROBLEM- > > Ignite 3 is the next major version of Apache Ignite. It targets the same > use cases and provides a similar set of features as Ignite 2. At the same > time, Ignite 2 and Ignite 3 are *technically* separate projects. They are > developed in different repositories (and therefore are based on different > codebases) and implement different internal architectures. To achieve a > more efficient development process, we need to create a clear separation > between 2.x and 3.x within *development resources* (Jira and Confluence). > > -POSSIBLE SOLUTIONS- > > 1. Create a separate Jira project and Confluence space for Ignite 3 > (initial suggestion). > 2. Add a *mandatory* field in Jira to identify whether a ticket belongs to > 2.x or 3.x. > > If we go with #2, there are still several things to figure out: > >- What is the name of this field? It needs to be intuitive to anyone who >joins the community. >- We need to make sure that Ignite 3 tickets are not mapped to 2.x >versions, and vice versa. Can we restrict this in Jira? Or we will have > to >monitor this manually? >- What do we do with Confluence? > > Nikolay, Ilya, Denis, and others who opposed the initial suggestion: if you > still prefer the second option, could you please address the points above? > I don't think it can be treated as an actual suggestion until we cover > these details. > > Let's discuss this until the end of the week. If there is no clear picture > on option #2 by then, I suggest we go with #1. > > -Val > > On Tue, Sep 28, 2021 at 11:22 PM Valentin Kulichenko < > valentin.kuliche...@gmail.com> wrote: > > > Folks, > > > > Versioning is a separate topic. We agreed on the current scheme in March > > [1]. If someone thinks we need to change it, please create a new thread > and > > present your suggestions. > > > > [1] > > > https://lists.apache.org/thread.html/r17ebaad35ca2bd70e716e67683ae7fec9bd97372b6cc57a7e9c81f9d%40%3Cdev.ignite.apache.org%3E > > > > -Val > > > > On Tue, Sep 28, 2021 at 12:37 PM Petr Ivanov > wrote: > > > >> Seems rational. > >> > >> > >> But still 2.11.0 and 21.1.0 for the time being will look like similar or > >> error in either version... > >> > >> > >> > On 27 Sep 2021, at 18:11, Ivan Pavlukhin wrote: > >> > > >> > I mean that Ignite 2.x will continue to use old scheme and Ignite 3 > >> > will be e.g. Ignite 21.1 and so on. > >> > > >> > 2021-09-27 14:57 GMT+03:00, Petr Ivanov : > >> >> How will not they clash if version is based only on date? > >> >> > >> >>> On 27 Sep 2021, at 14:33, Ivan Pavlukhin > wrote: > >> >>> > >> >>> Today it is quite common to use calendar-based versioning scheme, > e.g. > >> >>> [1]. We can consider it for Ignite 3. Luckily versions will not > clash. > >> >>> > >> >>> [1] https://www.cockroachlabs.com/docs/releases/index.html > >> >>> > >> >>> 2021-09-27 10:49 GMT+03:00, Petr Ivanov : > >> >>>> That name will definitely confuse Jira users. > >> >>>> > >> >>>> Let's stick to basic devision by 2.x and 3.x — it seems most > >> intuitive > >> >>>> and > >> >>>> has lots of examples inside ASF, look at the Tomcat for instance. > >> >>>> > >> >>>>> On 25 Sep 2021, at 21:05, Saikat Maitra > >> >>>>> wrote: > >> >>>>> > >> >>>>> Hi, > >> >>>>> > >> >>>>> I like the major version update like Ignite 3.0 but if we were to > >> come > >> >>>>> up > >> >>>>> with a name my other suggestion would be > >> >>>>> > >> >>>>> Ignite-kernel > >> >>>>> > >> >>>>> kernel - for the central or most important part of something > >> >>>>&g
Re: A new feedback has been added : 10
Hello! If we reply to users with emails, I suggest putting dev@ on CC. Regards, -- Ilya Kasnacheev чт, 23 сент. 2021 г. в 03:54, Nikita Safonov : > Hi Ilya! > > That’s a good point. I’d like to highlight that Ignite Doc Feedback service > credentials are stored here > <https://cwiki.apache.org/confluence/display/IGNITE/Ignite+PMC+Resources>, > so anyone can see the user’s feedback on bugyard.io. As for now, only me > and Igor Gusev are managing this. > But I do believe that 3 months (or any other period) shifts can be useful, > as well as periodic reports. > > By the way, we do reply to the users’ feedback with emails. What is more, > the work on the feedback can be tracked via Apache Ignite Jira tickets. > Every doc feedback ticket’s title starts with «Bugyard feedback #...». > > I guess that I’m ready to take this role and to discuss the volunteers for > the upcoming shifts later. > > With best regards, > Nikita > > вт, 21 сент. 2021 г. в 21:56, Ilya Kasnacheev : > > > Hello! > > > > Dear developers, I suggest we should have someone responsible for > handling > > bugyard reports and writing about that on developers list. > > > > Feedback is hidden behind login and I have no idea what's there, much > less > > if it was fixed. > > > > I think we should have a reply to every Bugyard e-mail and maybe > > three-month long shifts of people responsible for that. Anybody wishing > to > > take this role? > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пн, 20 сент. 2021 г. в 17:10, Bugyard : > > > > > A new feedback has been added, go to bugyard.io to see all the > > details... > > > > > > https://bugyard.io > > > > > > A new feedback has been added > > > > > > "Looks like [Running Ignite with Java 11 or later] link is broken." > by > > > tim239 > > > > > > View feedback > > > https://app.bugyard.io/web/app/rycqZJDyY/f/61488444507c91001448c81c > > >
Re: A new feedback has been added : 10
Hello! Dear developers, I suggest we should have someone responsible for handling bugyard reports and writing about that on developers list. Feedback is hidden behind login and I have no idea what's there, much less if it was fixed. I think we should have a reply to every Bugyard e-mail and maybe three-month long shifts of people responsible for that. Anybody wishing to take this role? Regards, -- Ilya Kasnacheev пн, 20 сент. 2021 г. в 17:10, Bugyard : > A new feedback has been added, go to bugyard.io to see all the details... > > https://bugyard.io > > A new feedback has been added > > "Looks like [Running Ignite with Java 11 or later] link is broken." by > tim239 > > View feedback > https://app.bugyard.io/web/app/rycqZJDyY/f/61488444507c91001448c81c
Re: Request for contributor permission
Hello! I have added you to Contributors role, you may assign tickets to yourself. Please make sure to read https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute Regards, -- Ilya Kasnacheev вт, 21 сент. 2021 г. в 17:54, Andrian Boşcanean : > Hello Ignite Community! > > My name is Andrian. I want to contribute to Apache Ignite and want to > start with this issue - IGNITE-15547, my JIRA username andrian.boscanean. > Any help on this will be appreciated. > > Thanks! > > On 2021/09/21 09:40:01, Andrian Boscanean > wrote: > > Dear all, > > > > Could I get contributors permission. > > > > Best regards, > > Andrian Boscanean > > >
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
Hello! + 0.5 I have got it to run with the following command: % COMPlus_EnableAlternateStackCheck=1 dotnet --fx-version 2.1.30 Apache.Ignite.dll I'm still confused by this publish/ directory. Why are we shipping something which is not for publishing in our binary package? I've also not heard of it before. Regards, -- Ilya Kasnacheev вт, 14 сент. 2021 г. в 12:37, Pavel Tupitsyn : > Ilya, > > > When I have also installed 3.1 and 2.0 > Please try .NET SDK 2.1 to run tests. > Yes, it went out of support last month, I've created a ticket [1]. > > > > dotnet Apache.Ignite.dll > That's correct, but should be done > in platforms/dotnet/bin/netcoreapp2.0/publish, please try again. > We should deal with duplicate binaries, I've created another ticket [2] > > > > Why do we still ship Apache.Ignite.exe if it does not run? > It runs on Windows. For Linux we ship Apache.Ignite.dll. > > > I don't think any of this is a blocker for the current release. > - Out-of-support SDK only affects those who build from source, and it went > out of support only recently > - Duplicate binaries are there for a long time and no one was complaining > > > [1] https://issues.apache.org/jira/browse/IGNITE-15504 > [2] https://issues.apache.org/jira/browse/IGNITE-15505 > > On Tue, Sep 14, 2021 at 11:58 AM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> > wrote: > > > Hello! > > > > - 0.5 > > > > Installed DEB package, built binary from source, ran sqlline, built .NET. > > > > I have failed to run .NET tests though. > > > > If I only install Current .NET, I get the following: > > It was not possible to find any compatible framework version > > The framework 'Microsoft.NETCore.App', version '2.0.0' was not found. > > > > > > - The following frameworks were found: > > > > > > 5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App] > > > > > > You can resolve the problem by installing the specified framework and/or > > SDK. > > > > > > The specified framework can be found at: > > > > > > - > > > > > https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App_version=2.0.0=x64=ubuntu.21.04-x64 > > > > When I have also installed 3.1 and 2.0, now I see: > > > > The active test run was aborted. Reason: Test host process crashed : No > > usable version of the libssl was found > > > > It looks like we have to bump the permitted .NET version. > > > > From the slim binary package I also can't run .NET: > > > > ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0% > > dotnet Apache.Ignite.dll > > Error: > > An assembly specified in the application dependencies manifest > > (Apache.Ignite.deps.json) was not found: > >package: 'System.Configuration.ConfigurationManager', version: '4.4.0' > >path: > 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll' > > > > Do we have any instructions on how to run it under Linux? Why do we still > > ship Apache.Ignite.exe if it does not run? > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>: > > > > > check again, 15503 not cherry-pick, right? > > > > > > 在 2021/9/14 15:55, Shishkov Ilya 写道: > > > >> Should the following two issue be merged into the ignite-2.11 > branch? > > > > Hi, as I see, both tickets are fixed in 2.10 and 2.11. > > > > > > > > вт, 14 сент. 2021 г. в 04:13, 18624049226<18624049...@163.com>: > > > > > > > >> Should the following two issue be merged into the ignite-2.11 > branch? > > > >> > > > >> https://issues.apache.org/jira/browse/IGNITE-14404 > > > >> > > > >> https://issues.apache.org/jira/browse/IGNITE-15503 > > > >> > > > >> 在 2021/9/13 17:12, Pavel Tupitsyn 写道: > > > >>> +1 > > > >>> > > > >>> Downloaded binary packages, started a cluster with a few nodes, > > tested > > > >> new > > > >>> .NET examples. > > > >>> > > > >>> On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky > > > >>>wrote: > > > >>> > > > >>>> Thanks Maxim ! > > > >>>> I tries to compare this ver with 2.10 (some performance tests with > > > >>>> persistence and transactional\atomic payload) and seems all ok >
Re: [VOTE] Release Apache Ignite 2.11.0 RC2
Hello! - 0.5 Installed DEB package, built binary from source, ran sqlline, built .NET. I have failed to run .NET tests though. If I only install Current .NET, I get the following: It was not possible to find any compatible framework version The framework 'Microsoft.NETCore.App', version '2.0.0' was not found. - The following frameworks were found: 5.0.9 at [/home/ilyak/.dotnet/shared/Microsoft.NETCore.App] You can resolve the problem by installing the specified framework and/or SDK. The specified framework can be found at: - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App_version=2.0.0=x64=ubuntu.21.04-x64 When I have also installed 3.1 and 2.0, now I see: The active test run was aborted. Reason: Test host process crashed : No usable version of the libssl was found It looks like we have to bump the permitted .NET version. >From the slim binary package I also can't run .NET: ~/D/apache-ignite-slim-2.11.0-bin/platforms/dotnet/bin/netcoreapp2.0% dotnet Apache.Ignite.dll Error: An assembly specified in the application dependencies manifest (Apache.Ignite.deps.json) was not found: package: 'System.Configuration.ConfigurationManager', version: '4.4.0' path: 'lib/netstandard2.0/System.Configuration.ConfigurationManager.dll' Do we have any instructions on how to run it under Linux? Why do we still ship Apache.Ignite.exe if it does not run? Regards, -- Ilya Kasnacheev вт, 14 сент. 2021 г. в 11:28, 18624049226 <18624049...@163.com>: > check again, 15503 not cherry-pick, right? > > 在 2021/9/14 15:55, Shishkov Ilya 写道: > >> Should the following two issue be merged into the ignite-2.11 branch? > > Hi, as I see, both tickets are fixed in 2.10 and 2.11. > > > > вт, 14 сент. 2021 г. в 04:13, 18624049226<18624049...@163.com>: > > > >> Should the following two issue be merged into the ignite-2.11 branch? > >> > >> https://issues.apache.org/jira/browse/IGNITE-14404 > >> > >> https://issues.apache.org/jira/browse/IGNITE-15503 > >> > >> 在 2021/9/13 17:12, Pavel Tupitsyn 写道: > >>> +1 > >>> > >>> Downloaded binary packages, started a cluster with a few nodes, tested > >> new > >>> .NET examples. > >>> > >>> On Mon, Sep 13, 2021 at 11:21 AM Zhenya Stanilovsky > >>>wrote: > >>> > >>>> Thanks Maxim ! > >>>> I tries to compare this ver with 2.10 (some performance tests with > >>>> persistence and transactional\atomic payload) and seems all ok there. > >>>> +1 from me. > >>>> > >>>>> Dear Community, > >>>>> > >>>>> > >>>>> The release candidate for the 2.11 version is ready. > >>>>> > >>>>> > >>>>> I have uploaded a release candidate to: > >>>>> https://dist.apache.org/repos/dist/dev/ignite/2.11.0-rc2/ > >>>>> https://dist.apache.org/repos/dist/dev/ignite/packages_2.11.0-rc2/ > >>>>> > >>>>> The following staging can be used for testing: > >>>>> > >> > https://repository.apache.org/content/repositories/orgapacheignite-1526/ > >> > https://www.myget.org/feed/apache-ignite-staging/package/nuget/Apache.Ignite > >>>>> Tag name is 2.11.0-rc2: > >>>>> > >> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=tag;h=refs/tags/2.11.0-rc2 > >>>>> RELEASE_NOTES: > >>>>> > >> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=RELEASE_NOTES.txt;hb=ignite-2.11 > >>>>> Complete list of resolved issues: > >>>>> > >> > https://issues.apache.org/jira/issues/?jql=(project%20%3D%20%27Ignite%27%20AND%20fixVersion%20is%20not%20empty%20AND%20fixVersion%20in%20(%272.11%27 > >>>> )) > >>>>> DEVNOTES: > >>>>> > >> > https://gitbox.apache.org/repos/asf?p=ignite.git;a=blob_plain;f=DEVNOTES.txt;hb=ignite-2.11 > >>>>> Additional checks have been performed (available for users included > >> into > >>>>> the release group on TeamCity). > >>>>> > >>>>> TC [Check RC: Licenses, compile, chksum] > >>>>> > >> > https://ci.ignite.apache.org/viewLog.html?buildId=6176219=ApacheIgniteReleaseJava8_PrepareVote4CheckRcLicensesChecksum=buildResultsDiv > >>>>> The vote is formal, see voting guidelines > >>>>> https://www.apache.org/foundation/voting.html > >>>>> > >>>>> +1 - to accept Apache Ignite 2.11.0-rc2 > >>>>> 0 - don't care either way > >>>>> -1 - DO NOT accept Apache Ignite Ignite 2.11.0-rc2 (explain why) > >>>>> > >>>>> See notes on how to verify release here > >>>>> https://www.apache.org/info/verification.html > >>>>> and > >>>>> > >> > https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-P5.VotingonReleaseandReleaseVerification > >>>>> This vote will be open for 4 days until Thu Sep 16, 12:00 2021 > (Moscow > >>>>> time). > >>>>> Please, write me down the thread if you need additional time to check > >>>>> the release. > >>>>> > >> > https://www.timeanddate.com/countdown/vote?iso=20210916T12=166=%5BVOTE%5D+Release+Apache+Ignite+2.10.0+RC2=serif=1 > >>>> > >>>> > >>>>
Re: A new feedback has been added : 7
Hello! https://ignite.apache.org/docs/latest/quick-start/python references to https://github.com/apache/ignite/tree/master/modules/platforms/python/examples which is 404 The first link on the page also points to itself. Regards, -- Ilya Kasnacheev сб, 11 сент. 2021 г. в 01:21, Bugyard : > A new feedback has been added, go to bugyard.io to see all the details... > > https://bugyard.io > > A new feedback has been added > > "Link to GitHub python example doesn't work." by mayankasthana1993 > > View feedback > https://app.bugyard.io/web/app/rycqZJDyY/f/613bd26c6f832300148dcc59
Re: KAFKA-IGNITE connector issues
Hello! Please write to u...@ignite.apache.org about this, since this list is dedicated to the discussion of development (and not usage) of Apache Ignite. Regards, -- Ilya Kasnacheev пт, 10 сент. 2021 г. в 13:34, shanshan Cheng : > Hello, > > I am an ignite user, recently I am connecting ignite and kafka in > distributed mode. > > The tests I did so far are: > 1. Initialize the sink connector and then connect kafka and ignite. It > worked. > 2. Initialize the source connector and connect kafka and ignite. It worked. > 3. Initialize the source and sink connectors together. The *error *I get is > when I Initialize both connectors at the same time, the sink connector > works fine, but the source connector disconnects automatically. > > So, my question is it possible to Initialize both connectors at the same > time? If it is possible, could you offer me a link to the document to see > the steps? > > Best regards >
Re: Ban Java Streams usage in Ignite 3 code
Hello! -1 Let's not ban Java Streams, for the reasons already listed. Regards, -- Ilya Kasnacheev чт, 9 сент. 2021 г. в 10:59, Ivan Daschinsky : > Few words about the topic. > There is a disease, quite common in the java community -- it is called the > streamosis. > But, to be honest, afear of streams is also not good. > > As for me, sometimes rewriting code completely with simple loops often > makes it more readable, understandable and usually faster. > > So I am against a complete ban of streams, but I am for using this tool > with caution. Often streams make code ugly and non-readable at all. > > > чт, 9 сент. 2021 г. в 10:50, Ivan Daschinsky : > > > To be honest, Pavel, your benchmark is not quite correct. Please, rewrite > > it using BlackHole > > > > чт, 9 сент. 2021 г. в 10:28, Nikolay Izhikov : > > > >> +1 to ban Streams usage. > >> > >> > >> > >> > 9 сент. 2021 г., в 02:59, Valentin Kulichenko < > >> valentin.kuliche...@gmail.com> написал(а): > >> > > >> > Pavel, > >> > > >> > Quite frankly, I think we used to lean into performance too much. We > >> > generally preferred it over data consistency, project modularity and > >> code > >> > readability. Performance, of course, plays a very important rule in > >> Ignite, > >> > but it's possible to overdo anything. > >> > > >> > There are certainly parts of the project that can benefit from > features > >> > like Stream API, without significant concern over performance. CLI is > an > >> > obvious example, but I'm sure it's not the only one. > >> > > >> > That said, I don't think that banning something is productive. At the > >> same > >> > time, we should make sure we pay more attention to performance during > >> > reviews. Maybe we should have a checklist of major things to look for? > >> Not > >> > as a set of strict rules, but more as a guideline for contributors and > >> > committers. > >> > > >> > We might also want to start benchmarking the code and tracking the > >> progress. > >> > > >> > -Val > >> > > >> > On Wed, Sep 8, 2021 at 12:09 PM Pavel Tupitsyn > >> wrote: > >> > > >> >> Alexander, Ivan, > >> >> > >> >>> not very productive to assume that 100% of your code is > >> >>> on the hot path > >> >> > >> >> That is exactly what we should be doing. > >> >> When I joined Ignite community 6 years ago, this was the prevalent > >> mindset. > >> >> > >> >> I'm not sure which part of Ignite can be considered "not on a hot > >> path". > >> >> Create/alter table (mentioned above) should perform well too. > >> >> > >> >>> measured first and only then optimized > >> >>> https://wiki.c2.com/?OptimizeLater > >> >> > >> >> Extra allocations are a "death by a thousand cuts". > >> >> They add up here and there, and then there are GC pauses. > >> >> This would be hard to "optimize later". > >> >> > >> >> It is common for perf-oriented projects to avoid some techniques. > >> >> For example, LINQ (streams analog from C# with similar perf issues) > is > >> >> avoided in libraries and compilers [1]. > >> >> > >> >> [1] https://github.com/dotnet/roslyn/blob/main/CONTRIBUTING.md > >> >> > >> >> On Wed, Sep 8, 2021 at 9:49 PM Valentin Kulichenko < > >> >> valentin.kuliche...@gmail.com> wrote: > >> >> > >> >>> I don't think we should ban anything. Streams API is just a tool in > >> the > >> >>> toolbox - it should be used appropriately. It's up to the > contributor > >> and > >> >>> reviewer(s) to identify whether a particular usage might cause > >> >> performance > >> >>> issues. > >> >>> > >> >>> -Val > >> >>> > >> >>> On Wed, Sep 8, 2021 at 8:01 AM Alexander Polovtcev < > >> >>> alexpolovt...@gmail.com> > >> >>> wrote: > >> >>> > >> >>>> -1 > >> >>>> I think that it is not very productive to assume that 100% of your > >> code > &g
Re: TC step problem
Hello! I guess the branch version should be 2.11 and not 2.11.0 since it is called ignite-2.11 Regards, -- Ilya Kasnacheev пт, 27 авг. 2021 г. в 11:41, Alexey Gidaspov : > Hi, ALL! > > I'm preparing vote for 2.11 release and tried to start compare with > previous release on TC [1]. Something's gone wrong. Can anyone tell what am > I doing wrong? > > [1] > https://ci.ignite.apache.org/buildConfiguration/ApacheIgniteReleaseJava8_IgniteRelease72CheckFileConsistency/6153997 >
[ANNOUNCE] Welcome Andrei Aleksandrov as a new committer
Hello! The Project Management Committee (PMC) for Apache Ignite has invited Andrei Aleksandrov to become a committer and we are pleased to announce that he has accepted. His experience with our processes and guidelines will allow him to assist other contributors who are trying to contribute a fix to some known issue in existing code, but find themself in need of guidance, review and then ensuring the code is included. Regards, -- Ilya Kasnacheev
Re: [Announcement] Apache Ignite 2.11 Code Freeze started
Hello! I think it does make sense to include changes which will let us avoid migration issues in the future. Alternatively, maybe we can revert the incomplete change from 2.11 in order to reintroduce it in 2.12 in full form if Igor agrees and RE thinks this is the best course of action. Regards, -- Ilya Kasnacheev чт, 29 июл. 2021 г. в 18:07, Igor Sapego : > Alexey, > > It contains changes we could not introduce if we release ignite in its > current state as they are going to be breaking changes. > > Best Regards, > Igor > > > On Thu, Jul 29, 2021 at 4:13 PM Alexey Gidaspov > wrote: > > > Hi, Igor! > > > > Now we are in stabilization phase and accepting only blockers. I may be > > wrong, but this ticket doesn't seem to be of that kind. > > > > On 2021/07/28 21:00:15, Igor Sapego wrote: > > > Igniters, > > > > > > I suggest adding [1] to the scope of release, because it contains > > > changes to code introduced by [2], which is already included in > release. > > > > > > [1] - https://issues.apache.org/jira/browse/IGNITE-14815 > > > [2] - https://issues.apache.org/jira/browse/IGNITE-14658 > > > > > > Best Regards, > > > Igor > > > > > > > > > On Mon, Jul 26, 2021 at 11:30 PM Maxim Muzafarov > > wrote: > > > > > > > Folks, > > > > > > > > The issues mentioned above were successfully resolved and > > > > cherry-picked to the ignite-2.11 branch. Sorry for the delay. I think > > > > we can proceed with the release. > > > > > > > > On Thu, 22 Jul 2021 at 15:44, Maxim Muzafarov > > wrote: > > > > > > > > > > Folks, > > > > > > > > > > Yes, both the fixes [1] [2] will not require performance tests > rerun. > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > On Thu, 22 Jul 2021 at 15:30, Dmitry Pavlov > > wrote: > > > > > > > > > > > > I personally trust opinion of Nikolay and Maxim, we can consider > > both > > > > as blockers. > > > > > > > > > > > > Just an idea to consider: > > > > > > For fixed ticket/PR ( > > > > https://issues.apache.org/jira/browse/IGNITE-15170) most likely we > > don't > > > > need to re-run performance tests. > > > > > > > > > > > > If second issue has no impact on performance, we can take perf > > results > > > > from rc.-1 and run only functional tests for rc.0. > > > > > > > > > > > > On 2021/07/22 04:44:01, "Николай Ижиков" > > wrote: > > > > > > > +1 to fix both prior to release > > > > > > > > > > > > > > Отправлено с iPhone > > > > > > > > > > > > > > > 22 июля 2021 г., в 02:36, Maxim Muzafarov > > > > > написал(а): > > > > > > > > > > > > > > > > Folks, > > > > > > > > > > > > > > > > We've faced [1][2] issues related to the new functionality > > added to > > > > > > > > the 2.11 release (it will be safe to merge to the release > > branch). > > > > > > > > From my point of view, both of them are critical and must be > > > > included > > > > > > > > in the 2.11 release. > > > > > > > > The [2] is ready for merge. The [1] will be completed by the > > end > > > > of this week. > > > > > > > > > > > > > > > > Please share your thoughts. > > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-15146 > > > > > > > > [2] https://issues.apache.org/jira/browse/IGNITE-15170 > > > > > > > > > > > > > > > >> On Tue, 20 Jul 2021 at 15:08, Maxim Muzafarov < > > mmu...@apache.org> > > > > wrote: > > > > > > > >> > > > > > > > >> Folks, > > > > > > > >> > > > > > > > >> Since the release branch was created some time ago, should > we > > > > bump up > > > > > >
Re: Review Requested -- IGNITE-15077
Hello! We now have 2 schedulers under the hood, whereas the optimal number is zero. I would very like to see a commit where the whole ignite-schedule package is sunsetted. With prior discussion on dev list, of course. I don't see the value of having local scheduling as part of Apache Ignite at all. It's very spotty and does not integrate with the rest of features. I know that GridGain makes use of the existing scheduling code, but since they do that on a separate code base they probably won't object to removal. If you plan on improving the Schedule module, instead of removing it, I would ask you to post a roadmap of that feature on the developers list, where you describe what you are planning to implement and why. Right now it is totally not obvious why I would use the new scheduleLocal methods instead of just adding Quartz to the project and calling that. Apache Ignite is not an universal middleware like Spring, it's a database. Regards, -- Ilya Kasnacheev чт, 29 июл. 2021 г. в 14:45, Andrey Mashenkov : > Atri. > > I think Ilya means IgniteCombinedSchedulerProcessor that delegates calls to > 2 different Scheduler implementations. > And the logic may not be enough clear for a user. > > 1. You added a new mandatory dependency on Quartz. > We are trying to avoid this as much as possible, because this may lead to > the jar-hell issue on the user-side. > E.g in case the user uses the same library of the other version for other > purposes. > > Is it possible to move scheduler implementation based on Quartz to a > separate module and make the module optional? > Or maybe move it to Ignite extensions? > > 2. Does it make sense to split Combined scheduler into 2 separate > implementations? > It looks ok if they will have slightly different capabilities on API if all > the limitations will be well-documented. > I mean Javadoc in implementation class must provide this information, along > with the common interface methods describe possible errors in a "@throw" > section in javadoc. > > > On Thu, Jul 29, 2021 at 1:15 PM Atri Sharma wrote: > > > Hi Ilya, > > > > Following up on this please. > > > > On Tue, 27 Jul 2021, 22:20 Atri Sharma, wrote: > > > > > Hi Ilya, > > > > > > > > > > Frankly speaking, I do not see the value of having an extra layer of > > > > indirection around *local* Quartz-based scheduler in Ignite. Can you > > > > elaborate? > > > > > > I didnt quite understand that. Are you referring to the > > > IgniteCombinedSchedulerProcessor? > > > > > > > > Our guidelines also recommend having issue description to document > the > > > whys > > > > and hows, and not just issue title. > > > > > > Sure, I will update the issue with more details. > > > > > > -- > > > Regards, > > > > > > Atri > > > Apache Concerted > > > > > > > > -- > Best regards, > Andrey V. Mashenkov >
Re: Your Nabble Forum
Hello! I think there's nothing which prevents Pony Mail from being indexed, it's just its SEO visibility is almost negligible. Regards, -- Ilya Kasnacheev ср, 28 июл. 2021 г. в 14:34, Denis Magda : > Alright, > > As long as our Nabble mail archive viewers went out of sync with the > community mailing lists, I posted a warning message on the Nabble home page > encouraging visitors to send questions to the list via an email client and > use Pony Mail as an archive viewer. Also, it's no longer possible to > create topics in Nabble or respond in existing discussions: > >- http://apache-ignite-developers.2346864.n4.nabble.com >- http://apache-ignite-users.70518.x6.nabble.com > > Also, I'm checking with INFRA if it's possible to enable indexing of the > archives in Pony Mail. > > - > Denis > > On Thu, Jul 22, 2021 at 3:56 PM Atri Sharma wrote: > > > Infra group is the ideal forum for this > > > > On Thu, 22 Jul 2021, 18:14 Denis Magda, wrote: > > > > > Dmitry, Ivan, > > > > > > It would be ideal if we can open up PonyMail archives for search > engines. > > > It might be just one setting on a web server configuration. Dmitry, any > > > idea whom we should start discussing this with at ASF? > > > > > > -- > > > Denis > > > > > > - > > > Denis > > > > > > On Thu, Jul 22, 2021 at 3:32 PM Ivan Daschinsky > > > wrote: > > > > > > > +1 for pony mail. It is a great tool with nice interface with zero > ads > > > > stuff. > > > > > > > > чт, 22 июл. 2021 г. в 15:26, Dmitry Pavlov : > > > > > > > > > Folks, > > > > > > > > > > My vote goes for ponymail. Actually it is a project under ASF > itself, > > > it > > > > > is the part of Incubator. > > > > > > > > > > If we have a contributor who is aware about CEO setup, we can > suggest > > > > help > > > > > and solve that issue for all ASF projects at once. > > > > > > > > > > https://github.com/apache/incubator-ponymail > > > > > https://ponymail.incubator.apache.org/support.html > > > > > https://lists.apache.org/list.html?us...@ponymail.apache.org > > > > > > > > > > I personaly use only lists.apache.org. And since at my dayjob > gmail > > is > > > > > blocked, I also reply here. > > > > > > > > > > What do you think? > > > > > > > > > > Sincerely, > > > > > Dmitriy Pavlov > > > > > > > > > > On 2021/07/22 10:58:28, Denis Magda wrote: > > > > > > Probably, this is a reason why our Nabble's dev list forum got > out > > of > > > > > sync. > > > > > > The latest message is dated as June 20th. > > > > > > > > > > > > Yeah, it's sad that ASF's mailing lists are not visible to search > > > > engines > > > > > > like Google. That's a big deal for those who search for a topic > on > > > > search > > > > > > engines (99% of the human beings?). Let's think, I see three > > options > > > > > here: > > > > > > > > > > > >- Search for an alternate mail archiving solution that can be > > > > indexed > > > > > by > > > > > >Google > > > > > >- Talk to the ASF mates, probably there is a solution for user > > > lists > > > > > >- Give up the reins to StackOverflow that will naturally > become > > a > > > > > >primary communication channel for the user-related questions. > > > > > > > > > > > > -- > > > > > > Denis > > > > > > > > > > > > - > > > > > > Denis > > > > > > > > > > > > On Thu, Jul 22, 2021 at 12:33 AM Ilya Kasnacheev < > > > > > ilya.kasnach...@gmail.com> > > > > > > wrote: > > > > > > > > > > > > > Hello! > > > > > > > > > > > > > > They say they don't host mailing list archives anymore. I > wonder > > > what > > > > > they > > > > > > > expect us to do here. > > > > > > > > > > > > > > I think it's a pity since Nabble had a great deal of SEO > > > visibility, > > > > > > > especially for user list. Unfortunately, Pony Mail is almost > > > useless > > > > in > > > > > > > that regard. > > > > > > > > > > > > > > Regards, > > > > > > > -- > > > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > > > > > > > ср, 21 июл. 2021 г. в 23:23, : > > > > > > > > > > > > > > > We are downsizing Nabble to one server. If you want to > > preserve > > > > your > > > > > > > > forum: > > > > > > > > > > > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/ > > > > > > > > > > > > > > > > Then you should follow the instructions here: > > > > > > > > > > > > > > > > http://support.nabble.com/Downsizing-Nabble-tp7609715.html > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Sincerely yours, Ivan Daschinskiy > > > > > > > > > >
Re: Review Requested -- IGNITE-15077
Hello! Frankly speaking, I do not see the value of having an extra layer of indirection around *local* Quartz-based scheduler in Ignite. Can you elaborate? Our guidelines also recommend having issue description to document the whys and hows, and not just issue title. Regards, -- Ilya Kasnacheev вт, 27 июл. 2021 г. в 18:42, Atri Sharma : > Hello, > > I have raised a PR for the said JIRA: > > https://github.com/apache/ignite/pull/9277 > > TC is green with the PR: > > > https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_BuildApacheIgnite/6105253 > > Please help in reviewing. > > Regards, > > Atri >
Re: Text Queries Support
> > > > All the Jira tickets we have on the Full-text search (FTS) thing are > > > targeted to Ignite 2. > > > > > > AFAIK, we want, but we have NOT committed to FTS support in Ignite 3, > > yet. > > > By the way, we are getting requests for this thing from the user side, > > and > > > definitely, > > > FTS would be a valuable feature for Ignite. > > > > > > It will be great if the one wants to drive it, any help will be > > appreciated. > > > > > > > > > On Fri, Jul 23, 2021 at 12:12 PM Atri Sharma wrote: > > > > > > > Hello, > > > > > > > > An update, please. I am working through persistence of Lucene index > > using > > > > Ignite Dictionary, and will be asking some questions soon. > > > > > > > > I had one doubt - - where does this change go? Ignite 3? > > > > > > > > Also, I know we want to build native support for text searches in > > Ignite 3. > > > > Is the work I am proposing here part of that, or will that be a > > separate > > > > effort? > > > > > > > > On Mon, 28 Jun 2021, 19:20 Ilya Kasnacheev, < > ilya.kasnach...@gmail.com > > > > > > > wrote: > > > > > > > > > Hello! > > > > > > > > > > I think that number one is the most important one, then maybe it > > will see > > > > > more use and other deficiencies become more apparent, leading to > more > > > > > tickets and visibility. > > > > > > > > > > Maybe 2. and 3. will even use a different approach when persistence > > is > > > > > implemented. > > > > > > > > > > Regards, > > > > > -- > > > > > Ilya Kasnacheev > > > > > > > > > > > > > > > пн, 28 июн. 2021 г. в 14:34, Atri Sharma : > > > > > > > > > > > Hello Again! > > > > > > > > > > > > I have been looking into the aforementioned and here are my > follow > > up > > > > > > thoughts: > > > > > > > > > > > > 1. Support persistence of Lucene indexes. > > > > > > 2. https://issues.apache.org/jira/browse/IGNITE-12401 (Needs > > fixing of > > > > > > moving partitions first) > > > > > > 3. Figure out how to return scores from nodes and use them as > sort > > > > > > parameters on the coordinator node > > > > > > (https://issues.apache.org/jira/browse/IGNITE-12291) > > > > > > > > > > > > Please let me know if this looks ok to make text queries > > functional? > > > > > > > > > > > > Atri > > > > > > > > > > > > On Mon, Jun 21, 2021 at 2:49 PM Alexei Scherbakov > > > > > > wrote: > > > > > > > > > > > > > > Hi. > > > > > > > > > > > > > > One of the biggest issues with text queries is a lack of > support > > for > > > > > > lucene > > > > > > > indices persistence, which makes this functionality useless if > a > > > > > > > persistence is enabled. > > > > > > > > > > > > > > I would first take care of it. > > > > > > > > > > > > > > пн, 21 июн. 2021 г. в 12:16, Maksim Timonin < > > timonin.ma...@gmail.com > > > > >: > > > > > > > > > > > > > > > Hi, Atri! > > > > > > > > > > > > > > > > You're right, Actually there is a lack of support for > > TextQueries. > > > > > For > > > > > > the > > > > > > > > last ticket I'm doing I see some obvious issues with them (no > > page > > > > > size > > > > > > > > support, for example). I'm glad that somebody wants to > maintain > > > > this > > > > > > > > functionality. Thanks a lot! > > > > > > > > > > > > > > > > For the MergeSort algorithm there is already a patch for that > > [1]. > > > > > It's > > > > > > > > currently on review. This patch introduces an abstract > reducer > > for > > > > > > > > CacheQueries
Re: Apache Ignite Repo 403 Forbidden
Hello! + Petr Bintray went away, and I guess we have to re-publish these to jfrog. Regards, -- Ilya Kasnacheev чт, 22 июл. 2021 г. в 20:39, Mustafa Sunka : > This looks very similar to an issue from last year: > > http://apache-ignite-users.70518.x6.nabble.com/Apache-Ignite-downloads-are-redirecting-from-https-to-http-td31428.html > > When I attempt to run `apt-get update` on Ubuntu 18.04 with the Apache > Ignite repository in /etc/apt/sources.list, the update fails due to an > https to http redirect. Here's the output from stdout: > > > WARNING: apt does not have a stable CLI interface. Use with caution in > scripts. > > Hit:1 http://azure.archive.ubuntu.com/ubuntu bionic InRelease > Get:2 http://azure.archive.ubuntu.com/ubuntu bionic-updates InRelease > [88.7 kB] > Get:4 http://azure.archive.ubuntu.com/ubuntu bionic-backports InRelease > [74.6 kB] > Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease > Hit:6 https://packages.microsoft.com/ubuntu/18.04/prod bionic InRelease > Err:3 https://dl.bintray.com/apache/ignite-deb apache-ignite InRelease > 403 Forbidden [IP: 52.38.32.109 443] > Reading package lists... > E: Failed to fetch > http://apache.org/dist/ignite/deb/dists/apache-ignite/InRelease 403 > Forbidden [IP: 52.38.32.109 443] > E: The repository 'http://apache.org/dist/ignite/deb apache-ignite > InRelease' is not signed. >
Re: Your Nabble Forum
Hello! They say they don't host mailing list archives anymore. I wonder what they expect us to do here. I think it's a pity since Nabble had a great deal of SEO visibility, especially for user list. Unfortunately, Pony Mail is almost useless in that regard. Regards, -- Ilya Kasnacheev ср, 21 июл. 2021 г. в 23:23, : > We are downsizing Nabble to one server. If you want to preserve your > forum: > > http://apache-ignite-developers.2346864.n4.nabble.com/ > > Then you should follow the instructions here: > > http://support.nabble.com/Downsizing-Nabble-tp7609715.html >
Re: Data out of sync between maillist and nabble.com
Hello! Nabble is an external resource and we do not have much say in how it works. I recommend using Apache's Pony Mail: https://lists.apache.org/list.html?dev@ignite.apache.org While not without drawbacks, it is overall an useful tool. Regards, -- Ilya Kasnacheev ср, 7 июл. 2021 г. в 04:36, 18624049226 <18624049...@163.com>: > Hi team, > > It seems that since mid June, the data between maillist and nabble.com > is no longer synchronized, which affects the user experience. > Is this a configuration error, or is a rule changed? > >
Re: [VOTE][EXTENSION] Release Apache Ignite spring-data-all-ext extensions 1.0.0 RC5
Hello! +1 (binding) The source zip now has the correct layout and builds OK. Regards, -- Ilya Kasnacheev пт, 2 июл. 2021 г. в 14:19, Maxim Muzafarov : > +1 (binding) > > On Fri, 2 Jul 2021 at 14:00, Nikolay Izhikov wrote: > > > > +1 (binding) > > > > > 1 июля 2021 г., в 08:35, Petrov Mikhail > написал(а): > > > > > > +1 > > > > > > Checked on Ubuntu 20.04. Created separate Spring Applications for each > version of Spring Data Integrations using the Maven RC repository and > following the documentation. Tested common use cases. Checked archive > signs. Built from the sources. > > > > > > On 01.07.2021 00:31, Sergei Ryzhov wrote: > > >> +1 > > >> Building modules from source and running tests successfully on Java 8 > > >> > > >> ср, 30 июн. 2021 г. в 16:02, Alex Plehanov : > > >> > > >>> +1 > > >>> > > >>> Check sha512, sign of archives and versions of released artifacts. > > >>> Check licenses with "mvn validate -DskipTests -P check-licenses" > > >>> Build modules from the source with Java 8 > > >>> Run examples: > > >>> from modules/spring-data-2.0-ext/examples with artifacts: Ignite > > >>> v2.10.0/ignite-spring-data-2.0-ext v1.0.0/spring-data v2.0 > > >>> from modules/spring-data-2.2-ext/examples with artifacts: Ignite > > >>> v2.10.0/ignite-spring-data-2.2-ext v1.0.0/spring-data v2.2 > > >>> > > >>> > > >>> ср, 30 июн. 2021 г. в 15:13, Nikita Amelchev : > > >>> > > >>>> Dear Ignite Community, > > >>>> > > >>>> I have uploaded a release candidate of the following extension > modules: > > >>>> > > >>>> spring-data-commons > > >>>> spring-data-ext > > >>>> spring-data-2.0-ext > > >>>> spring-data-2.2-ext > > >>>> > > >>>> The release candidate of the extensions: > > >>>> > > >>>> > > >>> > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-data-all-ext/1.0.0-rc5/ > > >>>> The instruction for building from the source package is placed in > the > > >>>> DEVNOTES file. > > >>>> > > >>>> The following staging can be used for testing: > > >>>> > https://repository.apache.org/content/repositories/orgapacheignite-1524 > > >>>> > > >>>> Tags were created: > > >>>> > > >>>> ignite-spring-data-commons-1.0.0-rc5 > > >>>> ignite-spring-data-ext-1.0.0-rc5 > > >>>> ignite-spring-data-2.2-ext-1.0.0-rc5 > > >>>> ignite-spring-data-2.0-ext-1.0.0-rc5 > > >>>> ignite-spring-data-all-ext-1.0.0-rc5 > > >>>> > > >>>> > > >>> > https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=4a3ba7b542c46501d425dfa378ac8670e253f49a > > >>>> RELEASE NOTES: > > >>>> > > >>>> > > >>> > https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=22f8d665c194ba2dfa6167354d97ad53d5ef206f;hb=c8de80ee14d1fb76d6cbb0b18513bb70b499c3cb > > >>>> DOCUMENTATION: > > >>>> Documentation of listed extensions was updated in the following > issues: > > >>>> > > >>>> > > >>> > https://issues.apache.org/jira/issues/?filter=-1=key%20in%20(IGNITE-14662%2CIGNITE-14398%2CIGNITE-14493) > > >>>> The vote is formal, see voting guidelines > > >>>> https://www.apache.org/foundation/voting.html > > >>>> > > >>>> +1 - to accept all the Apache Ignite spring-data-all-ext extensions > > >>>> 1.0.0-rc5 listed in the thread > > >>>> 0 - don't care either way > > >>>> -1 - DO NOT accept either of the Apache Ignite spring-data-all-ext > > >>>> extensions 1.0.0-rc5 (explain why) > > >>>> > > >>>> The vote will hold for 3 days and will end on July 3 2021 13:00 UTC > > >>>> > > >>>> > > >>> > https://www.timeanddate.com/countdown/generic?iso=20210703T13=0=cursive > > >>>> -- > > >>>> Best wishes, > > >>>> Amelchev Nikita > > >>>> > > >> > > >
Re: [VOTE][EXTENSION] Release Apache Ignite performance-statistics-ext extension 1.0.0 RC4
Hello! -1 (binding) I did not check the rest of the package, but both of zip deliverables suffer from having a lot of files at the root of zip file. - ignite-performance-statistics-ext-1.0.0-bin.zip <https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-performance-statistics-ext/1.0.0-rc4/ignite-performance-statistics-ext-1.0.0-bin.zip> should have ignite-performance-statistics-ext-1.0.0-bin/ as a root directory and nothing else on the 1st level - ignite-performance-statistics-ext-1.0.0-src.zip <https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-performance-statistics-ext/1.0.0-rc4/ignite-performance-statistics-ext-1.0.0-src.zip> should have ignite-performance-statistics-ext-1.0.0-src/ as a root directory and nothing else on the 1st level. While we are waiting for rebuild, I hope other users will try the actual functionality. Regards, -- Ilya Kasnacheev вт, 29 июн. 2021 г. в 01:51, Saikat Maitra : > +1 > > On Fri, Jun 25, 2021 at 6:34 AM Sergei Ryzhov > wrote: > > > +1 > > > > -- > > Best regards, > > Sergei Ryzhov > > >
Re: Defrag?
Hello! Is it WAL (wal/) that is growing or checkpoint space (db/)? If latter, any specific caches that are growing unbound? If letter, you can try creating a new cache, moving the relevant data to this new cache, switch to using it, and then drop the old cache - should reclaim the space. Regards, -- Ilya Kasnacheev пн, 28 июн. 2021 г. в 17:34, Ryan Trollip : > Is this why the native disk storage just keeps growing and does not reduce > after we delete from ignite using SQL? > We are up to 80GB on disk now on some instances. We implemented a custom > archiving feature to move older data out of ignite cache to a PostgresSQL > database but when we delete that data from ignite instance, the disk data > size ignite is using stays the same, and then keeps growing, and > growing > > On Thu, Jun 24, 2021 at 7:10 PM Denis Magda wrote: > >> Ignite fellows, >> >> I remember some of us worked on the persistence defragmentation features. >> Has it been merged? >> >> @Valentin Kulichenko probably you know >> the latest state. >> >> - >> Denis >> >> On Thu, Jun 24, 2021 at 11:59 AM Ilya Kasnacheev < >> ilya.kasnach...@gmail.com> wrote: >> >>> Hello! >>> >>> You can probably drop the entire cache and then re-populate it via >>> loadCache(), etc. >>> >>> Regards, >>> -- >>> Ilya Kasnacheev >>> >>> >>> ср, 23 июн. 2021 г. в 21:47, Ryan Trollip : >>> >>>> Thanks, Ilya, we may have to consider moving back to non-native storage >>>> and caching more selectively as the performance degrades when there is a >>>> lot of write/delete activity or tables with large amounts of rows. This is >>>> with SQL with indexes and the use of query plans etc. >>>> >>>> Is there any easy way to rebuild the entire native database after >>>> hours? e.g. with a batch run on the weeknds? >>>> >>>> On Wed, Jun 23, 2021 at 7:39 AM Ilya Kasnacheev < >>>> ilya.kasnach...@gmail.com> wrote: >>>> >>>>> Hello! >>>>> >>>>> I don't think there's anything ready to use, but "killing performance" >>>>> from fragmentation is also not something reported too often. >>>>> >>>>> Regards, >>>>> -- >>>>> Ilya Kasnacheev >>>>> >>>>> >>>>> ср, 16 июн. 2021 г. в 04:39, Ryan Trollip : >>>>> >>>>>> We see continual very large growth to data with ignite native. We >>>>>> have a very chatty use case that's creating and deleting stuff often. The >>>>>> data on disk just keeps growing at an explosive rate. So much so we >>>>>> ported >>>>>> this to a DB to see the difference and the DB is much smaller. I was >>>>>> searching to see if someone has the same issue. This is also killing >>>>>> performance. >>>>>> >>>>>> Founds this: >>>>>> >>>>>> https://cwiki.apache.org/confluence/display/IGNITE/IEP-47%3A+Native+persistence+defragmentation >>>>>> >>>>>> Apparently, there is no auto-rebalancing of pages? or cleanup of >>>>>> pages? >>>>>> >>>>>> Has anyone implemented a workaround to rebuild the cache and indexes >>>>>> say on a weekly basis to get it to behave reasonably? >>>>>> >>>>>> Thanks >>>>>> >>>>>
Re: Publishing Spring Sessions to Maven Repo
Hello! It is being voted on currently, but will need one more round probably. Regards, -- Ilya Kasnacheev пн, 28 июн. 2021 г. в 14:35, Atri Sharma : > Gentle ping > > On Thu, Jun 24, 2021 at 6:36 PM Atri Sharma wrote: > > > > Hi All, > > > > Can we please publish Spring Sessions Ext artifacts to the Maven repo? > > > > Atri > > > > -- > Regards, > > Atri > Apache Concerted >
Re: Text Queries Support
Hello! I think that number one is the most important one, then maybe it will see more use and other deficiencies become more apparent, leading to more tickets and visibility. Maybe 2. and 3. will even use a different approach when persistence is implemented. Regards, -- Ilya Kasnacheev пн, 28 июн. 2021 г. в 14:34, Atri Sharma : > Hello Again! > > I have been looking into the aforementioned and here are my follow up > thoughts: > > 1. Support persistence of Lucene indexes. > 2. https://issues.apache.org/jira/browse/IGNITE-12401 (Needs fixing of > moving partitions first) > 3. Figure out how to return scores from nodes and use them as sort > parameters on the coordinator node > (https://issues.apache.org/jira/browse/IGNITE-12291) > > Please let me know if this looks ok to make text queries functional? > > Atri > > On Mon, Jun 21, 2021 at 2:49 PM Alexei Scherbakov > wrote: > > > > Hi. > > > > One of the biggest issues with text queries is a lack of support for > lucene > > indices persistence, which makes this functionality useless if a > > persistence is enabled. > > > > I would first take care of it. > > > > пн, 21 июн. 2021 г. в 12:16, Maksim Timonin : > > > > > Hi, Atri! > > > > > > You're right, Actually there is a lack of support for TextQueries. For > the > > > last ticket I'm doing I see some obvious issues with them (no page size > > > support, for example). I'm glad that somebody wants to maintain this > > > functionality. Thanks a lot! > > > > > > For the MergeSort algorithm there is already a patch for that [1]. It's > > > currently on review. This patch introduces an abstract reducer for > > > CacheQueries with 2 implementations (unordered, merge-sort). Then > TextQuery > > > leverages on MergeSort to order results from multiple nodes by score. > This > > > patch also fixes the pageSize issue, I've mentioned before. Could you > > > please check if it fully matches your idea? Any issues or comments are > > > welcome. > > > > > > I've prepared this ticket, because I need the MergeSort algorithm for > the > > > new type of queries I'm implementing (IndexQuery, it should also > provide > > > ordered results over multiple nodes). Currently I'm not planning to go > > > further with TextQuery, so if you're going to support this it'll be a > great > > > contribution, I think. > > > > > > [1] https://issues.apache.org/jira/browse/IGNITE-14703 > > > [2] https://github.com/apache/ignite/pull/9081 > > > > > > > > > On Mon, Jun 21, 2021 at 11:11 AM Atri Sharma wrote: > > > > > > > Hi All, > > > > > > > > I have been looking into our text queries support and see that it has > > > > limited community support. > > > > > > > > Therefore, I volunteer to be the maintainer of the module and work on > > > > enhancing it further. > > > > > > > > First goal would be to move to Lucene 8.x, then work on sorted reduce > > > > - merge across nodes. Fundamentally, this is doable since Lucene > ranks > > > > documents according to their score, and documents are returned in the > > > > order of their score. Since the scoring function is homogeneous, this > > > > means that across nodes, we can compare scores and merge sort. > > > > > > > > Please let me know if I can take this up. > > > > > > > > Atri > > > > > > > > -- > > > > Regards, > > > > > > > > Atri > > > > Apache Concerted > > > > > > > > > > > > > -- > > > > Best regards, > > Alexei Scherbakov > > -- > Regards, > > Atri > Apache Concerted >
Re: [VOTE][EXTENSION] Release Apache Ignite spring-data-all-ext extensions 1.0.0 RC4
Hello! -1 (binding) The root element of the source zip file should be ignite-spring-data-all-ext-1.0.0-src/ directory. No other directories/files should be at the root of the source zip file. This is a *blocker* but should be very straightforward to fix. Regards, -- Ilya Kasnacheev пт, 25 июн. 2021 г. в 17:46, Sergei Ryzhov : > +1 > Building modules from source and running tests successfully on Java 8 > > пт, 25 июн. 2021 г. в 16:52, Alex Plehanov : > > > +1 > > > > Check sha512, sign of archives and versions of released artifacts (BTW, > > version of parent artifact is 1.0.0-SNAPSHOT, I don't think it's a > blocker > > now, but it's better to be fixed in the next releases). > > Check licenses with "mvn validate -DskipTests -P check-licenses" > > Build modules from the source (Note: build successfully on Java 8, but > > build on Java 11 has failed due to maven-javadoc-plugin. To build on Java > > 11 I have used this command: "mvn clean install -DskipTests > > -Dmaven.javadoc.skip=true") > > Run examples (create new maven project and copy sources from examples > > directories): > > from modules/spring-data-2.0-ext/examples with artifacts: Ignite > > v2.10.0/ignite-spring-data-2.0-ext v1.0.0/spring-data v2.0 > > from modules/spring-data-2.2-ext/examples with artifacts: Ignite > > v2.10.0/ignite-spring-data-2.2-ext v1.0.0/spring-data v2.2 > > > > пт, 25 июн. 2021 г. в 16:26, Ilya Kasnacheev >: > > > > > Hello! > > > > > > The contents of the source package are much more reasonable now. > However, > > > there's still an issue that root element of zip archive is not a > > directory: > > > ~/Downloads/spring% unzip ignite-spring-data-all-ext-1.0.0-src.zip > > > Archive: ignite-spring-data-all-ext-1.0.0-src.zip > > > creating: checkstyle/ > > > inflating: checkstyle/checkstyle-suppressions.xml > > > inflating: checkstyle/checkstyle.xml > > > creating: config/ > > > inflating: config/example-ignite.xml > > > creating: modules/ > > > creating: modules/spring-data-2.0-ext/ > > > inflating: modules/spring-data-2.0-ext/README.txt > > > > > > > > > whereas > > > ~/Downloads% unzip -l apache-ignite-2.8.1-src.zip| head > > > Archive: apache-ignite-2.8.1-src.zip > > > 864220966caa4157c4fee8a1bc85171623963604 > > > Length DateTimeName > > > - -- - > > >0 2020-05-21 16:42 apache-ignite-2.8.1-src/ > > > 2029 2020-05-21 16:42 apache-ignite-2.8.1-src/.gitignore > > >0 2020-05-21 16:42 apache-ignite-2.8.1-src/.idea/ > > >0 2020-05-21 16:42 > > > apache-ignite-2.8.1-src/.idea/inspectionProfiles/ > > >80905 2020-05-21 16:42 > > > apache-ignite-2.8.1-src/.idea/inspectionProfiles/Project_Default.xml > > > 5119 2020-05-21 16:42 apache-ignite-2.8.1-src/CONTRIBUTING.md > > > > > > > > > The root element of source sip should > > > be ignite-spring-data-all-ext-1.0.0-src/ directory. > > > > > > This is a small issue but a *blocker*, maybe you can do a quick > rebuild? > > > > > > Another issue is that I don't understand how to run examples. If I add > > the > > > entire directory as maven project, the examples/main directory is not > > > considered source root and will not be built/run > > > Maybe I'm missing something. > > > > > > Can you add is as an additional sources root, perhaps? You can even > > build a > > > jar with classifier 'examples' if that's OK. > > > > > > Regards, > > > > > > -- > > > Ilya Kasnacheev > > > > > > > > > пт, 25 июн. 2021 г. в 14:17, Mikhail Petrov : > > > > > > > +1 > > > > > > > > Checked on Ubuntu 20.04. Created separate Spring Applications for > each > > > > version of Spring Data Integrations using the Maven RC repository and > > > > following the documentation. Tested common use cases. > > > > > > > > On 25.06.2021 12:43, Nikita Amelchev wrote: > > > > > Dear Ignite Community, > > > > > > > > > > I have uploaded a release candidate of the following extension > > modules: > > > > > > > > > > spring-data-commons > > > > > spring-data-ext > > > > > spring-data-2.0-ext > > > > > spring-data-2.2-ext > > > >
Re: [VOTE][EXTENSION] Release Apache Ignite spring-data-all-ext extensions 1.0.0 RC4
Hello! The contents of the source package are much more reasonable now. However, there's still an issue that root element of zip archive is not a directory: ~/Downloads/spring% unzip ignite-spring-data-all-ext-1.0.0-src.zip Archive: ignite-spring-data-all-ext-1.0.0-src.zip creating: checkstyle/ inflating: checkstyle/checkstyle-suppressions.xml inflating: checkstyle/checkstyle.xml creating: config/ inflating: config/example-ignite.xml creating: modules/ creating: modules/spring-data-2.0-ext/ inflating: modules/spring-data-2.0-ext/README.txt whereas ~/Downloads% unzip -l apache-ignite-2.8.1-src.zip| head Archive: apache-ignite-2.8.1-src.zip 864220966caa4157c4fee8a1bc85171623963604 Length DateTimeName - -- - 0 2020-05-21 16:42 apache-ignite-2.8.1-src/ 2029 2020-05-21 16:42 apache-ignite-2.8.1-src/.gitignore 0 2020-05-21 16:42 apache-ignite-2.8.1-src/.idea/ 0 2020-05-21 16:42 apache-ignite-2.8.1-src/.idea/inspectionProfiles/ 80905 2020-05-21 16:42 apache-ignite-2.8.1-src/.idea/inspectionProfiles/Project_Default.xml 5119 2020-05-21 16:42 apache-ignite-2.8.1-src/CONTRIBUTING.md The root element of source sip should be ignite-spring-data-all-ext-1.0.0-src/ directory. This is a small issue but a *blocker*, maybe you can do a quick rebuild? Another issue is that I don't understand how to run examples. If I add the entire directory as maven project, the examples/main directory is not considered source root and will not be built/run Maybe I'm missing something. Can you add is as an additional sources root, perhaps? You can even build a jar with classifier 'examples' if that's OK. Regards, -- Ilya Kasnacheev пт, 25 июн. 2021 г. в 14:17, Mikhail Petrov : > +1 > > Checked on Ubuntu 20.04. Created separate Spring Applications for each > version of Spring Data Integrations using the Maven RC repository and > following the documentation. Tested common use cases. > > On 25.06.2021 12:43, Nikita Amelchev wrote: > > Dear Ignite Community, > > > > I have uploaded a release candidate of the following extension modules: > > > > spring-data-commons > > spring-data-ext > > spring-data-2.0-ext > > spring-data-2.2-ext > > > > The release candidate of the extensions: > > > https://dist.apache.org/repos/dist/dev/ignite/ignite-extensions/ignite-spring-data-all-ext/1.0.0-rc4/ > > > > The instruction for building from the source package is placed in the > > DEVNOTES file. > > > > The following staging can be used for testing: > > https://repository.apache.org/content/repositories/orgapacheignite-1520 > > > > Tags were created: > > > > ignite-spring-data-commons-1.0.0-rc4 > > ignite-spring-data-ext-1.0.0-rc4 > > ignite-spring-data-2.2-ext-1.0.0-rc4 > > ignite-spring-data-2.0-ext-1.0.0-rc4 > > ignite-spring-data-all-ext-1.0.0-rc4 > > > https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=commit;h=56db147fc059f3a64e0c00fe9d0a9d0d70ec97b0 > > > > RELEASE NOTES: > > > https://gitbox.apache.org/repos/asf?p=ignite-extensions.git;a=blob;f=RELEASE_NOTES.txt;h=22f8d665c194ba2dfa6167354d97ad53d5ef206f;hb=c8de80ee14d1fb76d6cbb0b18513bb70b499c3cb > > > > DOCUMENTATION: > > Documentation of listed extensions was updated in the following issues: > > > https://issues.apache.org/jira/issues/?filter=-1=key%20in%20(IGNITE-14662%2CIGNITE-14398%2CIGNITE-14493) > > > > The vote is formal, see voting guidelines > > https://www.apache.org/foundation/voting.html > > > > +1 - to accept all the Apache Ignite spring-data-all-ext extensions > > 1.0.0-rc4 listed in the thread > > 0 - don't care either way > > -1 - DO NOT accept either of the Apache Ignite spring-data-all-ext > > extensions 1.0.0-rc4 (explain why) > > > > The vote will hold for 5 days and will end on May 30 2021 10:00 UTC > > > https://www.timeanddate.com/countdown/generic?iso=20210630T10=0=cursive > > >
