search-engine

Elasticsearch Version

7.16.3

Installed Plugins

No response

Java Version

bundled

OS Version

Windows 10

Problem Description

I'm looking into a report of a bug raised against the .NET client for use of search templates. The root cause seems to be that while the [REST API spec](https://github.com/elastic/elast

Discussed with @Kerollmops
As we did for the tokenizer, we want to use the heed dependency from Milli's side to avoid having different versions of Heed in Meilisearch. Indeed compilation will fail if we have different versions of heed in Meilisearch and in Milli.

• Export heed on Milli's side
• Use the exported Heed dependency in

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.

chrono seems to be unmaintained and depends on an outdated version of time. For all features required by the engine and the API time should suffice.

As chrono types and modules are re-exported by the public API this will be a breaking change. I also suggest to use this opportunity for removing those re-exports from the API which IMHO do not provide any value and are more confusing than

Describe the feature you'd like to see added

Current the /search endpoint returns a HTML file to display the results. This works well for UI users, which might be the first use case of Whoogle. But it's hard for prog

Is your feature request related to a problem? Please describe.
There seems to be duplication of logic in the code for Cloud Plugins. This is an opportunity for us to streamline the codebase and refactor these classes. This issue stems from these comments in #2096.

Describe the solution you'd like

_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

... to make it easier to read Vespa documentation on an e-reader / offline

Vespa documentation is generated using Jekyll from .md and .html files, look into options for generating the artifact as part of site generation (there might be plugins we can use here)

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