-
Notifications
You must be signed in to change notification settings - Fork 24.4k
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
[Transform] Transform fails for unsigned long fields #63871
Labels
Comments
Pinging @elastic/ml-core (:ml/Transform) |
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this issue
Oct 20, 2020
writing out integer results properly, because coerce is not supported for unsigned_long fixes elastic#63871
hendrikmuhs
pushed a commit
that referenced
this issue
Oct 20, 2020
add support for unsigned_long, which required a change in writing out integer results properly, because coerce is not supported for unsigned_long fixes #63871
This was referenced Oct 20, 2020
hendrikmuhs
pushed a commit
that referenced
this issue
Oct 20, 2020
hendrikmuhs
pushed a commit
that referenced
this issue
Oct 20, 2020
pugnascotia
pushed a commit
to pugnascotia/elasticsearch
that referenced
this issue
Oct 21, 2020
add support for unsigned_long, which required a change in writing out integer results properly, because coerce is not supported for unsigned_long fixes elastic#63871
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#60050 introduced a new field type
unsigned_long
. Transform fails in certain combinations if the source index uses a field mapped tounsigned_long
.Repro steps:
failure:
Root cause: Transform indexes the output as string as it does not know that
unsigned_long
is a numeric type, which is due to the addition ofunsigned_long
as plugin.Non-Issue: Because
unsigned_long
support has not been released yet, this issue is not a bug by definition. It's still important to fix.Blocker: In order to not become a bug, I classify it as blocker.
The text was updated successfully, but these errors were encountered: