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
[ML] Filtering category runtime fields in advanced wizard #132916
[ML] Filtering category runtime fields in advanced wizard #132916
Conversation
@@ -16,6 +16,13 @@ import { | |||
} from '../types/fields'; | |||
import { ML_JOB_AGGREGATION } from '../constants/aggregation_types'; | |||
|
|||
const categoryFieldTypes = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
moving this into common
Pinging @elastic/ml-ui (:ml) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM 🎉 |
@peteharverson i've added sorting to all the field list dropdowns in c69a52d |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Edit to fix sorting LGTM
💚 Build SucceededMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
* [ML] Filtering category runtime fields in advanced wizard * reverting accidentally commited code * sorting fields in dropdowns * removing accidentally committed code (cherry picked from commit ad36a63)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…132987) * [ML] Filtering category runtime fields in advanced wizard * reverting accidentally commited code * sorting fields in dropdowns * removing accidentally committed code (cherry picked from commit ad36a63) Co-authored-by: James Gowdy <jgowdy@elastic.co> Co-authored-by: Spencer <spencer@elastic.co>
When using runtime fields in the advanced job wizard, category fields, e.g. keyword, text, should not be selectable as the detector's
field_name