Tiny supportability nit: today we emit these log messages when adding a write block to an index:

[2022-03-22T19:43:26,897][INFO ][o.e.c.m.MetadataIndexStateService] [node_t1] adding block write to indices [[test-blocks/eLkrYpm_S3WNemfWpXrhPA]]
[2022-03-22T19:43:26,933][INFO ][o.e.c.m.MetadataIndexStateService] [node_t1] completed adding block write to indices [test-blocks]

This is

Since

• we have to test the dump behavior manually
• we often get bug reports during pre-release regarding the dumps

We might want to add a CI testing the dumps behavior

• Using each already created dump file on our public S3
  • try to import them into Meilisearch and check it was well imported (same documents, same key

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.

Expose a public API for interacting with JSON field types outside of the QueryParser

As of right now, there is no way to public way to build queries to interact with the new JSON field type outside of the QueryParser,
due to the JsonTermWriter not being publically exposed, and also possibly slightly overkill.

Ideally a simple(ish) API allows users to produce a term to query with by sup

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

Describe the bug
OpenSearch is able to warn a use about upcoming deprecation of API used. Some of deprecation messages refers to Elasticsearch version instead of OpenSearch.
There are deprecations seen by .Net client automated test:

299 OpenSearch-1.3.0-e45991597c86ba1bbcc36ee1dfdc165197a913af "Parameter [boost] on field [name] is deprecated and will be removed in 8.0"
299 OpenS

Problem
Currently FARMReader will ask users to raise max_seq_length every time some samples are longer than the value set to it. However, this can be confusing if max_seq_length is already set to the maximum value allowed by the model, because raising it further will cause hard-to-read CUDA errors.

See #2177.

Solution
We should find a way to query the model for the maximum va

... 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