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

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

Kibana version: master (~7.14)
Describe the bug:

Human-readable duration field formatter outputs a few seconds for 0 value

Steps to reproduce:

1. Create a duration human-readable field formatter on index pattern
2. Check-in discover how a 0 value shown as a few seconds

Expected behavior:

I think we should output 0 following other formatting options. e.g

As suggested in the ESM guidelines of Node.js it would be good to explicit the type of the module.

{
+  "type": "commonjs",
}