-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[Transform] transform fails with "specified fields can't be null or empty" #67333
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Pinging @elastic/ml-core (:ml/Transform) |
This was referenced Jan 12, 2021
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Jan 12, 2021
…elastic#67334) avoid illegal argument exception when fields is empty, which is a valid case fixes elastic#67333
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Jan 12, 2021
…elastic#67334) avoid illegal argument exception when fields is empty, which is a valid case fixes elastic#67333
This was referenced Jan 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
found by @szabosteve
Affected versions: 7.9.3 - 7.11.0
The transform fails calling
_preview
or on_start
with the error message:specified fields can't be null or empty
. This happens for transforms that don't use anyfield
parameter in eithergroup_by
oraggregation
, e.g. because ingroup_by
/aggregation
only scripts are used or afilter
aggregation without a child aggregation (for a full example see below).Mitigation:
Create the destination index, before starting the transform yourself, e.g.
PUT myindex
.or
Add an aggregation that uses a
field
into your config, e.g:Solution:
The bug is a regression of #62945. In a special case transform tries to retrieve field capabilities for 0 fields, which is not allowed.
full failure example:
Error:
The text was updated successfully, but these errors were encountered: