Closed c-dante closed 5 years ago
Thanks for reporting @c-dante , this issue is already fixed by https://github.com/elastic/elasticsearch/pull/41280 that assumes that any unmapped field is of type keyword (and not numeric as it is today).
Cool -- saw in that thread that it should have made it into 7.1.x
and the timing lined up commit wise, but I see the 7.2.0
tag now.
Using docker image:
docker.elastic.co/elasticsearch/elasticsearch:7.1.1
Elasticsearch version (
bin/elasticsearch --version
): 7.1.1Plugins installed: []
JVM version (
java -version
):OS version (
uname -a
if on a Unix-like system):Linux amp 5.0.13-arch1-1-ARCH #1 SMP PREEMPT Sun May 5 18:05:41 UTC 2019 x86_64 GNU/Linux
Description of the problem including expected versus actual behavior: Expected: Running a composite aggregate with
after
on dynamic, alias'd indexes don't fail on undefined fields.Actual: If an aliased index is missing a field, it crashes with number format excetion
Steps to reproduce: Here's a gist with the set up + logs https://gist.github.com/c-dante/9c973425f0dfd6ed3b22ec0c538e03e8
Spark notes of the process:
_templates/my-idx
)/my-idx-default
)/my-idx-content
)/my-idx
)after
, it crashes with number format.This looks to be a further case of https://discuss.elastic.co/t/rollup-job-numberformatexception/178195
Provide logs (if relevant): Here's a shorter snippet of the logs, gist has full from request
And the response: