Currently, it's possible to create an ILM policy with a Delete phase with an empty actions object so that the phase doesn't contain a delete action. This will result in a policy that will not delete indices.
How to reproduce:

PUT _ilm/policy/my_policy
{
  "policy": {
    "phases": {
      "delete": {
        "actions": {}
      }
    }
  }
}

It's a detail, but we should manage payload limit size in a human readable fashion like at least MB. I don't see a scenario where someone would like to increase or decrease the limit for a byte.

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

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