Skip to content
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

[BUG] Can no longer run transform jobs that contain a script within an aggregation #1107

Open
Bit-64 opened this issue Feb 9, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Bit-64
Copy link

Bit-64 commented Feb 9, 2024

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?

  • Version v 2.11.0
@Bit-64 Bit-64 added bug Something isn't working untriaged labels Feb 9, 2024
@dblock
Copy link
Member

dblock commented Jun 17, 2024

Looks like a possible regression, were you able to narrow this down further @Bit-64 ?

Catch All Triage - 1 2 3 4 5

@dblock dblock removed the untriaged label Jun 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants