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

Blacklist a number of prediction field names. #49371

Closed

Conversation

przemekwitek
Copy link
Contributor

This PR prevents field name clashes in ml results docs on JSON level.

Closes #48808

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

@przemekwitek
Copy link
Contributor Author

Abandoning this PR in favor of elastic/ml-cpp#861 which implements the same logic but in C++. Thanks to this, there is no coupling introduced between C++ and Java wrt ml results format.

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

Successfully merging this pull request may close these issues.

[ML] 'prediction_field_name' accepts values that clash with already existing fields
4 participants