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 /

Check with our PR @gmourier, this addition can be implemented by the community 🎉

Currently, the search engine does not highlight the number in _formatted because it's impossible to add <em> tag around a number (not a string) in JSON.

What we expect?
Return the raw document (so the number) but the "transformed" document (so with the number surrounded of the tag in a string) in `

Is your feature request related to a problem? Please describe.

I just cannot receive any response from bing.com.

Describe the solution you'd like

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

When I use latest rest client, it brings with it a dependency of an old async http client (httpasyncclient-4.1.4.jar).
This client is no longer maintained. See its github page: https://github.com/apache/httpasyncclient

Not only this is a security risk, I also believe that using this old client causes multiple issues, and also related to :
https://github.com/spring-projects/spring-data-elasti

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

Many users in our community have been asking to have easier ways to return the output of intermediate nodes. I can see that this could be very useful for debugging and also qualitative evaluation.

I think this feature would be very useful, though the exact design is not yet fully clear.

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