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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *Test with high flaky rate in master-nightly IgniteRebalanceScheduleResendPartitionsTest.test

Re: [ANNOUNCE] Apache Ignite spring-data-all-ext extensions 1.0.0 released

Igniters, It seems that these artifact have not been uploaded to Maven Repo? Will it be uploaded with ignite 2.11? This release does not include spring-tx-ext, but the documentation of this artifact has been merged into the ignite-2.11 branch, What's wrong? 在 2021/7/7 下午1:49, Nikita

Re: Text Queries Support

Atri, Sure, go ahead. Let's put the ideas on paper and have a discussion. -Val On Fri, Jul 23, 2021 at 10:59 AM Atri Sharma wrote: > Thanks Andrey. > > I have collected answers or proposals to many of these questions and > would like to start a wiki page covering what we can do for Ignite 3.

Re: Text Queries Support

It surely will not be supported out of the box, but in my understanding Calcite provides enough flexibility for us to develop these features in a way we would like to see them. Andrey, please correct me if I am wrong here. -Val On Fri, Jul 23, 2021 at 10:58 AM Atri Sharma wrote: > The

Re: Text Queries Support

Thanks Andrey. I have collected answers or proposals to many of these questions and would like to start a wiki page covering what we can do for Ignite 3. Does that sound good, please? On Fri, Jul 23, 2021 at 4:26 PM Andrey Mashenkov wrote: > > Atri, > > First of all, I'd recommend going

Re: Text Queries Support

The standard ways to deal with text based searches in SQL are the CONTAINS operator, the LIKE operator or specific functions (REGEXP_MATCHES, for eg). I do not think any of these are supported by Calcite at the moment. On Fri, Jul 23, 2021 at 11:20 PM Valentin Kulichenko wrote: > > In my

Re: Text Queries Support

In my experience, one of the biggest usability issues with the current support of text queries is that they are completely decoupled from SQL. I.e. you can either execute a SQL query OR a text query. Modern databases, on the other hand, typically allow creating text-based indexes within regular

Re: [DISCUSS] Confuse default inspections.

-0 for both proposals I agree with Ivan Daschinsky, we should not mix both approaches (interfaces with "public" keyword and without "public" keyword), but I see no big difference between "require public keyword in interfaces" rule and "prohibit public keyword in interfaces" rule. To switch from

Re: Apache Ignite 3 Alpha 2 webinar follow up questions

Andrey, Thanks for the response - see my comments inline. > I've gone through the questions and have no the whole picture of your use > case. Would you please clarify how you exactly use the Ignite? what are the > integration points? > I'll try to clarify - we have a low/no code platform. A

Re: [VOTE] Release pyignite 0.5.1-rc0

+1 From me 1. Checked binary packages, c module and examples on windows 10 amd64 for pythons 3.6, 3.7, 3.8, 3.9 2. Checked binary packages, c module and examples on ubuntu 20.04 amd64 for pythons 3.6, 3.7, 3.8, 3.9 3. Checked source installation and building binary packages on ubuntu 20.04 amd 64

Re: Apache Ignite Repo 403 Forbidden

Petr, Yes, everything has been migrated to JFrog and is available with PMC credentials. https://apache.jfrog.io/ui/login/ On Fri, 23 Jul 2021 at 13:58, Petr Ivanov wrote: > > Yes, it is. > > Seems that Apache kept the storage, or JFrog helped somehow. > Some one from committer side should

Re: Apache Ignite Repo 403 Forbidden

Yes, it is. Seems that Apache kept the storage, or JFrog helped somehow. Some one from committer side should update http://apache.org/dist/ignite/deb link to redirect correctly. Not sure though there is still a way to deliver new packages there. > On 23 Jul 2021, at 13:19, Maxim Muzafarov

Re: Text Queries Support

Atri, First of all, I'd recommend going through the Ignite ticket to gather information about the current implementation issues and users' wants. Then look at a code to get a complete understanding of how things work now, which may help in future decisions. As we use the outdated Lucene version,

Re: [VOTE] Release pyignite 0.5.1-rc0

The voting finishes at 07/27/2021 12:00 UTC пт, 23 июл. 2021 г. в 13:49, Ivan Daschinsky : > Dear Igniters! > > Release candidate binaries for subj are uploaded and ready for vote > You can find them here: > https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.1-rc0 > > If you follow the

[VOTE] Release pyignite 0.5.1-rc0

Dear Igniters! Release candidate binaries for subj are uploaded and ready for vote You can find them here: https://dist.apache.org/repos/dist/dev/ignite/pyignite/0.5.1-rc0 If you follow the link above, you will find source packages (*.tar.gz and *.zip) and binary packages (wheels) for windows

Re: Apache Ignite Repo 403 Forbidden

Folks, Artefacts are available here. Is this what we are looking for? https://apache.jfrog.io/artifactory/ignite-deb/ https://apache.jfrog.io/artifactory/ignite-rpm/ On Fri, 23 Jul 2021 at 12:15, Petr Ivanov wrote: > > No mirror. > > Also

Re: Text Queries Support

I am actually happy to drive the feature for Ignite 3. FTS is very important for me and I think Ignite users will benefit from it greatly. If it makes sense to be focusing on Ignite 3 for this capability, I am eager to contribute there and lead the development. Please share your thoughts. On

Re: Text Queries Support

Hi Atri, 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

Re: Apache Ignite Repo 403 Forbidden

No mirror. Also http://apache.org/dist/ignite/deb/dists/apache-ignite/InRelease is redirected to Bintray which is closed. The only way to get packages now — get source code for corresponding release version and build package

Re: Text Queries Support

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

Re: Apache Ignite 3 Alpha 2 webinar follow up questions

Courtney, I have a short update. > 3. The Lucene API enabled more flexibility and removed a network > round trip from our queries. > 4. Given Calcite's ability to support custom SQL functions, I'd love > to have the ability to define custom functions that Lucene was answering As