Alex Klibisz

Results 62 issues of Alex Klibisz

Thanks for putting this project together. Is there any way a table or small list could be included to describe which libraries support incremental item additions? I imagine for many...

### Background The current custom benchmark suite is difficult to use, maintain, and share results. A custom solution made sense originally, as it was intended for large-scale distributed benchmarks, e.g.,...

### Support guidelines - [X] I've read the [support guidelines](https://github.com/alexklibisz/elastiknn/blob/master/readme.md#support) ### Background Running the RecallSuite in Github Actions to merge an unrelated PR. Examples: #399 , #398 , #397 ....

bug

- Upgrade Elasticsearch from 7.17.3 to Elasticsearch 8.8.0 - Upgrade Lucene from 8.11.1 to Lucene 9.0.0 - Upgrade elastic4s from 7.17.2 to 8.0.0 - Make the `index.elastiknn` setting a no-op...

### Background As the title suggests, migrate from Scala 2.13 to Scala 3. As per #392 , I do not plan to publish libraries, and so I do not plan...

### Background To my knowledge, the Scala and Java libraries are not used anywhere outside of this project. They are quite tedious to maintain. Sonatype is a surprisingly flaky and...

### Background This has been requested a few times in the past. It didn't seem pertinent as Elastiknn started on Elasticsearch 7.x. Now it's a bit of a blocker for...

Now that Lucene 8.8 supports configurable docvalues compression, I would ideally be able to remove the index.elastiknn setting and just let users decide whether they want to optimize for search...

There are some alternatives that are likely to be a better long-term choice. See discussion here: https://www.reddit.com/r/java/comments/m4b9f6/downsides_to_using_sunmiscunsafe_for/

performance

**Describe the bug** Elastiknn exceptions do not extend ElasticsearchException, so they seem to always be turned into a 500, when a 4xx would often be more appropriate. **Expected behavior** -...

bug
good first issue