What is the bug?
I currently have a transform job that I run periodically that used to run just fine on v2.7. Since upgrading to v2.11, the transform now fails with an error I have never seen before. I’ve had no issues running the transform aggregation without a proper field and only a script prior. If I add a bogus field to the aggregation, it runs just fine, but obviously without aggregating on the return value of the script. The aggregation still runs just fine outside of a transform in a normal search query.
How can one reproduce the bug?See here for configuration and current output error.
What is the expected behavior?
Expect the transform job to run using the return value of the script as the field to aggregate on.
dblock
commented
3 months ago
What is the bug? I currently have a transform job that I run periodically that used to run just fine on v2.7. Since upgrading to v2.11, the transform now fails with an error I have never seen before. I’ve had no issues running the transform aggregation without a proper field and only a script prior. If I add a bogus field to the aggregation, it runs just fine, but obviously without aggregating on the return value of the script. The aggregation still runs just fine outside of a transform in a normal search query.
How can one reproduce the bug? See here for configuration and current output error.
What is the expected behavior? Expect the transform job to run using the return value of the script as the field to aggregate on.
What is your host/environment?