search-engine

We should ignore java.io.tmpdir and override it with ES_TMPDIR. I think that variable should be taken into account from the beginning of startup scripts (including JavaVersionChecker) and the value should be applied as java option to all java processes.

Java processes started before ES_JAVA_OPTS are parsed (JavaVersionChecker, TempDirectory, JvmOptionParser) can also create temporary files in /

⚠️ Should be done once meilisearch/MeiliSearch#1897 is merged

We should find a way to have only one file related to the docker image CI instead of two, for maintenance reasons.

Here are the current files:

• https://github.com/meilisearch/MeiliSearch/blob/main/.github/workflows/publish-docker-latest.yml: publish the git tag as docker tag
• https://github.com/meilisea

Currently when clicking an image from search resutls the pop-up includes the image at a fixed size.
I propose to either increase that scaling to a somewhat higher fixed value or factor in the original image size so that very small pictures do not become pixelated.

Currently the preview is too small in my opinion which forces me to visit the website.

Right now the documentation page for https://docs.rs/tantivy/latest/tantivy/termdict/type.TermDictionary.html renders almost empty without listing methods and other item info. This could be the case for other types as well.

This task is to check the documentation rendered at https://docs.rs/tantivy/latest/tantivy and fix pages that are not rendering documentation content.

Make the search box larger or make the texts inside the search box smaller would potentially solve the issue.

Describe the bug
Gradle scripts are configuring destructiveDistroTest.docker task twice and we see warning with run.

> Configure project :qa:os
Cannot add task 'destructiveDistroTest.docker' as a task with that name already exists.
=======================================
OpenSearch Build Hamster says Hello!
  Gradle Version        : 7.3
  OS Info               : Mac OS X 10.16 

Hi Team,

I have created a vespa multinode stack and performed a load test for search query

1. search with single field with 60s timeout - median was consistent around 150 to 200ms
   endpoint : /search/
   http request : POST
   Body:
   {
   "yql":"select * from sources * where table contains "testing.vespa.search"
   }
2. search with more fields and conditions - median was 100+ secs which is very

_handle_duplicate_documents and _drop_duplicate_documents in the elastic search document store will always report self.index as the index with the conflict, which is obviously incorrect.

Edit: Upon further investigation, this is actually a lot worse. Using multiple indices with the ElasticSearch DocumentStore is completely broken due to the fact, that this is used in `_handle_duplicate_do

What happened

Accidentally omitting document content returns 500 Internal Server Error with a body of {"message":"Internal error","uri":"/new_index"}

What was expected

Emitting any kind of helpful message would be helpful. Also, in my experience, when the client receives a 500 response, there is usually something informative on the server-side. But in this case, the server e

I am finding a product which can replace Elasticsearch.

People are interested in a size-comparison between

• tinysearch
• lunr.js
• elasticlunr
• flexsearch
• fuse.js

If anyone wants to do a comparison, post a comment here.
Some ideas:

• Use an open dataset, e.g. Shakespeare texts https://shakespeare.folger.edu/download/
• Create a size histogram of the results that we can include into the README.
• Add the code to the repository under a `b