-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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] Data frame analytics analysis stats #53788
[ML] Data frame analytics analysis stats #53788
Conversation
Adds parsing and indexing of analysis instrumentation stats. The latest one is also returned from the get-stats API. Note that we chose to duplicate objects even where they are currently similar. There are already ideas on how these will diverge in the future and while the duplication looks ugly at the moment, it is the option that offers the highest flexibility.
Pinging @elastic/ml-core (: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.
I have an overall concern with HLRC.
By making these fields ctor
parse fields unboxed and mandatory, we restrict hlrc compatibility as it cannot ever handle those fields becoming optional or being null
.
Do you think we should all these to be optional (at least when parsing from xcontent). We can still make them mandatory in the object by unboxing to zero values.
...rc/main/java/org/elasticsearch/client/ml/dataframe/stats/classification/Hyperparameters.java
Outdated
Show resolved
Hide resolved
...rc/main/java/org/elasticsearch/client/ml/dataframe/stats/classification/Hyperparameters.java
Outdated
Show resolved
Hide resolved
...el/src/main/java/org/elasticsearch/client/ml/dataframe/stats/classification/TimingStats.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/elasticsearch/client/ml/dataframe/stats/classification/ValidationLoss.java
Outdated
Show resolved
Hide resolved
...l/src/main/java/org/elasticsearch/client/ml/dataframe/stats/outlierdetection/Parameters.java
Outdated
Show resolved
Hide resolved
.../main/java/org/elasticsearch/xpack/core/ml/dataframe/stats/outlierdetection/TimingStats.java
Outdated
Show resolved
Hide resolved
...re/src/main/java/org/elasticsearch/xpack/core/ml/dataframe/stats/regression/TimingStats.java
Outdated
Show resolved
Hide resolved
...src/main/java/org/elasticsearch/xpack/core/ml/dataframe/stats/regression/ValidationLoss.java
Outdated
Show resolved
Hide resolved
...va/org/elasticsearch/xpack/core/ml/action/GetDataFrameAnalyticsStatsActionResponseTests.java
Outdated
Show resolved
Hide resolved
.../src/main/java/org/elasticsearch/client/ml/dataframe/stats/outlierdetection/TimingStats.java
Outdated
Show resolved
Hide resolved
@benwtrent I addressed your comments. For now I made fields optional where necessary and kept them simply boxed. |
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.
two things, both I think are just copy-paste type errors. Once those are cool, should be good to go :D
...l/src/main/java/org/elasticsearch/client/ml/dataframe/stats/outlierdetection/Parameters.java
Outdated
Show resolved
Hide resolved
...va/org/elasticsearch/xpack/core/ml/action/GetDataFrameAnalyticsStatsActionResponseTests.java
Outdated
Show resolved
Hide resolved
Until elastic#53788 is backported to 7.x.
Until #53788 is backported to 7.x.
Adds parsing and indexing of analysis instrumentation stats. The latest one is also returned from the get-stats API. Note that we chose to duplicate objects even where they are currently similar. There are already ideas on how these will diverge in the future and while the duplication looks ugly at the moment, it is the option that offers the highest flexibility. Backport of #53788
... after backporting elastic#53788
... after backporting #53788
Adds parsing and indexing of analysis instrumentation stats.
The latest one is also returned from the get-stats API.
Note that we chose to duplicate objects even where they are currently
similar. There are already ideas on how these will diverge in the future
and while the duplication looks ugly at the moment, it is the option
that offers the highest flexibility.