Ryan Bogan
Ryan Bogan
Possible Routes : - Job Scheduler as a Module * Multiple plugins already have a dependency on job-scheduler (one to many relationship) * Plugins / extensions can directly extend Job...
@dblock @kartg @nknize @Bukhtawar @praveensameneni @owaiskazi19 @anasalkouz @reta @bbarani @mch2 @andrross @peternied @saratvemulapalli @anirudha Many of you were involved in previous discussions about the location of Job Scheduler, and we...
> Can we improve this experience so that the onus is on the _upstream plugin_ rather than the _user_ to install job-scheduler? It seems like there's an opportunity here to...
> I'm actually quite confused how this is a different issue than [opensearch-project/job-scheduler#147](https://github.com/opensearch-project/job-scheduler/issues/147) where there was strong opposition to moving it to the core. > > Tangentially, it looks like...
Based on the feedback provided, we have decided to proceed with moving Job Scheduler to a native plugin.
@kavilla @nknize said offline that he did not have any concerns about moving Job Scheduler to a native plugin and agreed with our decision. The questions posed above were for...
Following a deep dive, we throw the nested circuit breaker exception in KNNVectorFieldMapper [here](https://github.com/opensearch-project/k-NN/blob/main/src/main/java/org/opensearch/knn/index/mapper/KNNVectorFieldMapper.java#L625-L631). This method is called within a parseCreateField [method](https://github.com/opensearch-project/k-NN/blob/main/src/main/java/org/opensearch/knn/index/mapper/KNNVectorFieldMapper.java#L546). Tracing the method calls, we eventually arrive at...
@UsenkoArtem I don’t believe there is currently a way to stop training gracefully, since the majority of the training process happens in the JNI layer. From my understanding, we prevent...
Collapse is currently not supported for hybrid query, but we are working to implement it. From my understanding, the collapse processor works with hybrid query. You can attach the processor...
@ankitas3 You are correct, that is a limitation of using the collapse processor. We are working to support adding collapse to a hybrid query, but it is currently not supported....