I currently use the legacy IndexTemplates with the "inheritance" mechanism.
During runtime, my application, will read in plain JSON templates from the filesystem and make PutIndexTemplateRequests out of the content using the standard "source(Map<String, Object>)" API available in all Request subclasses to fill the request with the relevant content.

Now, that those templates are becoming legacy

Describe the bug
When entering a search in the provided MeiliSearch dashboard the search is broken, returning a 400 error as the & breaks the search request URL. This is because the search string is not URL encoded using encodeURIComponent(search.value).

• https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent

To Reproduce
Steps to r

The DocStore builds blocks of contiguous document serialized in an adhoc simple binary format.
These blocks are then compressed.

The format goes:

• field: u32
• type tag: u8
• value: specific to the type but for instance u64 simply take 8 byts.

@ppodolsky noticed that despite the compression, it might be possible to shave off a few percent of storage by changing the encoding. This might

PrestoDB https://prestodb.io .. is widely used as SQL frontend for many different data-sources, including ElasticSearch, and even files in S3 .. would be very nice if there would be a Connector available for Vespa.

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

The author of failure himself says so here https://internals.rust-lang.org/t/failure-crate-maintenance/12087/3.