Skip to content

Conversation

@polyfractal
Copy link
Contributor

Backport of #52851

We weren't originally going to backport this, but then the VS refactor landed in 7.x sooner than expected, so this should come too. But it got held up by other parts that had to be backported / fixed first. :)

…lastic#52851)

SigTerms cannot run on fields that are not searchable, and SigText
cannot run on fields that do not have analyzers.  Both of these
situations fail today with an esoteric exception, so this just formalizes
the constraint by throwing an IllegalArgumentException up front.

In practice, the only affected field seems to be the `binary` field,
which is neither searchable or has a default analyzer (e.g. even numeric
and keyword fields have a default analyzer despite not being tokenized)

Adds supported-type tests, and makes some changes to the test itself
to allow testing sigtext (indexing _source).

Also a few tweaks to the test to avoid bad randomization (negative
numbers, etc).
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-analytics-geo (:Analytics/Aggregations)

@elasticmachine elasticmachine added the Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) label Jun 1, 2020
@polyfractal polyfractal merged commit 79ac69c into elastic:7.x Jun 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Analytics/Aggregations Aggregations backport Team:Analytics Meta label for analytical engine team (ESQL/Aggs/Geo) v7.9.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants