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

[Transform] Search runtime fields are not handled properly during mapping deduction. #68516

Closed
przemekwitek opened this issue Feb 4, 2021 · 4 comments · Fixed by #68970
Closed
Labels

Comments

@przemekwitek
Copy link
Contributor

Since not available via FieldCapabilities API, transform search runtime fields are not "visible" to the mapping deduction code.
Therefore, the destination index is missing mappings for the aggregation fields based on search runtime fields.
This affects aggregations that copy the mapping type from source (min, max) but not the aggregations that use a fixed mapping type (avg).

@przemekwitek przemekwitek self-assigned this Feb 4, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml/Transform)

@jimczi
Copy link
Contributor

jimczi commented Feb 4, 2021

We are working on a solution for this, see #68117. You shouldn't need to reimplement that logic, it's much simpler to just rely on field capabilities to do it for you.

@przemekwitek
Copy link
Contributor Author

We are working on a solution for this, see #68117.

Thanks @jimczi . Sounds like that's exactly what we need. Is this enhancement targeted at 7.12 or later?

@przemekwitek
Copy link
Contributor Author

FTR, the fix was implemented using the new FieldCapabilitiesRequest.runtime_fields feature mentioned by @jimczi above.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants