Elasticsearch version (bin/elasticsearch --version): 7.12.1

Plugins installed: []

JVM version (java -version):

OS version (uname -a if on a Unix-like system):

Description of the problem including expected versus actual behavior:

ILM Rollover max_docs o

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.

Hi, phrase query is too strict now, is there any plan to support slop?

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

Is your feature request related to a problem? Please describe.
If you work on domain corpora, collecting additional training data to improve your reader or retriever models is very helpful.
For collecting training data, there are two main options:
a) Manual Labelling
b) User feedback for "live predictions"

b) is particularly promising if you don't have enough time or resources for a)

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