Skip to content

Blacklist a number of prediction field names.#49371

Closed
przemekwitek wants to merge 2 commits intoelastic:masterfrom
przemekwitek:disallow_field_name_clash
Closed

Blacklist a number of prediction field names.#49371
przemekwitek wants to merge 2 commits intoelastic:masterfrom
przemekwitek:disallow_field_name_clash

Conversation

@przemekwitek
Copy link
Copy Markdown

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

Closes #48808

@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/ml-core (:ml)

@przemekwitek
Copy link
Copy Markdown
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