[DISCUSS] dependencies and release process for Ignite Extensions

Hello, I wanted to connect and discuss on the release process for ignite-extensions. As of today all our integrations since released together were able to run build based on latest snapshot for example the current build depends on 2.8.0-SNAPSHOT. If we are making ignite-extensions as separate

Re: [DISCUSS] Pub/Sub Streamer Implementation

Hi Emmanouil, I have added you as contributor in Ignite Extensions project. Can you please check and confirm if you are able to see the project and execute build on your pull request. Regards, Saikat On Tue, Nov 26, 2019 at 12:49 PM Emmanouil Gkatziouras wrote: > Hi all! > > If someone could

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

I don't see anything wrong if Yuriy is willing to carry on and keep enhancing our full-text search support that lacks basic capabilities. The basics should be available. If anybody needs an advanced feature they can introduce Solr or ElastiSearch into the final architecture of the app. Folks,

Re: [DISCUSS] Pub/Sub Streamer Implementation

Hi all! If someone could give me read access to the Job of Ignite Extensions on Team City will greatly help me (username gkatzioura). I suppose the builds get triggered automatically on a pull request. Kind regards, Emmanouil *Emmanouil Gkatziouras* https://egkatzioura.com/ |

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

Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. *New Critical Failure in master Platform C++ (Linux)* https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_PlatformCLinux?branch=%3Cdefault%3E No changes in the build

RE: Re: Thin client: compute support

Alex, >Filtering logic for OP_CLUSTER_GROUP_GET_NODE_IDS looks overcomplicated. Do >we need server-side filtering at all? Wouldn't it be better to send basic >info (ids, order, flags) for all nodes (there is relatively small amount of >data) and extended info (attributes) for selected list

[jira] [Created] (IGNITE-12397) Apache spark - org.apache.ignite.IgniteIllegalStateException

Shenson Joseph created IGNITE-12397: --- Summary: Apache spark - org.apache.ignite.IgniteIllegalStateException Key: IGNITE-12397 URL: https://issues.apache.org/jira/browse/IGNITE-12397 Project: Ignite

[jira] [Created] (IGNITE-12396) [ML] Random Forest generates NaN for a part of models on small datasets

Alexey Zinoviev created IGNITE-12396: Summary: [ML] Random Forest generates NaN for a part of models on small datasets Key: IGNITE-12396 URL: https://issues.apache.org/jira/browse/IGNITE-12396

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

Folks, IEP is an Ignite-specific thing. In fact, I suppose that we are already doing it in ASF way by having this dev-list discussion =) As for me, implementing "limit" feature for text queries is not so big to make an IEP. But we might need to create one for next features. вт, 26 нояб. 2019 г.

Re: Thin client: compute support

> After all, we don't cancel request We do cancel a request to perform a task. We may and should use this to cancel any other request in future. > Client uses some cluster group filtration (for example forServers() cluster group) Please see above - Aleksandr Shapkin described how we store

Re: Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

Hello! ASF way should probably start with an IEP :) Regards, -- Ilya Kasnacheev вт, 26 нояб. 2019 г. в 14:12, Zhenya Stanilovsky : > > Ok, lets forgot Solr and go through ASF way, if Yuriy prove this > functionality is helpful and PR it, why not ? > > isn`t it ? > > >Вторник, 26 ноября 2019,

Re[4]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

Ok, lets forgot Solr and go through ASF way, if Yuriy prove this functionality is helpful and PR it, why not ?   isn`t it ?   >Вторник, 26 ноября 2019, 14:06 +03:00 от Ilya Kasnacheev >: >  >Hello! > >The problem here is that Solr is a multi-year effort by a lot of people. We >can't match

Re: Re[2]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

Hello! The problem here is that Solr is a multi-year effort by a lot of people. We can't match that. Maybe we could integrate with Solr/Solr Cloud instead, by feeding our cache information into their storage for indexing and relying on their own mechanisms for distributed IR sorting? Regards,

Re[2]: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

Ilya Kasnacheev, what a problem in Solr with Ignite functionality ?   thanks !   >Вторник, 26 ноября 2019, 13:50 +03:00 от Ilya Kasnacheev >: >  >Hello! > >I have a hunch that we are trying to build Apache Solr (or Solr Cloud) into >Apache Ignite. I think that's a lot of effort that is not very

Re: Text queries/indexes (GridLuceneIndex, @QueryTextFiled)

Hello! I have a hunch that we are trying to build Apache Solr (or Solr Cloud) into Apache Ignite. I think that's a lot of effort that is not very justified. I don't think we should try to implement sorting in Apache Ignite, because it is a lot of work, and a lot of code in our code base which we

Re: Thin client: compute support

> Anyway, my point stands. I can't agree. Why you don't want to use task id for this? After all, we don't cancel request (request is already processed), we cancel the task. So it's more convenient to use task id here. > Can you please provide equivalent use case with existing "thick" client? For

Re: Thin client: compute support

> I can't see any usage of request id in query cursors You are right, cursor id is a separate thing. Anyway, my point stands. > client sends long term tasks to nodes and wants to do it with load balancing I still don't get it. Can you please provide equivalent use case with existing "thick"