While the output in the UI was fine, certain job configurations containing non-aggregatable fields could trigger errors on the Elasticsearch side. This PR fixes it by adding an additional query for fieldCaps to check first which fields are actually aggregatable. |
||
---|---|---|
.. | ||
client | ||
lib | ||
models | ||
routes |