search-engine

It would be nice if the _close (and _open) endpoints would accept a body with the index name(s) to operate on.
In my use case calling <indexname>/_close is not allowed, but calling _close with a body that holds a list of indices to close would be possible.

cc @DaveCTurner @henningandersen as we talked about this

Describe the bug

I would like to create a new API key with restricted permissions on a given index. The API returns an error when I specify the action documents.*. According to the documentation of v0.25,

The * character can also be used as a wildcard to get all permissions for a route, e.g. documents.* to authorize acc

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.

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
TL;DR: same issue reported here.

Per ElasticSearch's 7.10 documentation (which AFAICT should be compatible with OpenSearch 1.x), setting term_vector on a search_as_you_type field should only affect the shingle s

Proposed changes:

• Section that tells the reader about what companies already use Haystack, this helps strengthen the horizontal relationships in the community

The inspiration is taken from the Apache Superset repository

Status (please check what you already did):

• First draft (up for discussions & feedb

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