-
Notifications
You must be signed in to change notification settings - Fork 25.6k
[ML] Documentation for Data Frame Analytics high-level REST client #42288
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] Documentation for Data Frame Analytics high-level REST client #42288
Conversation
|
Pinging @elastic/ml-core |
6c13b18 to
ca6d517
Compare
...high-level/src/test/java/org/elasticsearch/client/documentation/MlClientDocumentationIT.java
Outdated
Show resolved
Hide resolved
...high-level/src/test/java/org/elasticsearch/client/documentation/MlClientDocumentationIT.java
Outdated
Show resolved
Hide resolved
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.
This should have callouts defined, and the match_all default mention should be in the callout for setQuery
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.
Done
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.
Do we want to document the OutlierDetection builder methods here as well? There are zero java docs for the class. We need to have at least some documentation (preferably here AND some java docs on the methods) on the builder methods.
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.
To make this future-proof, I think we should refer from here to another section where we will list creation of the various analysis types.
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.
Added a section about analysis. Not sure though how detailed it should be.
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.
Also add analyzed fields
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.
To make this future-proof, I think we should refer from here to another section where we will list creation of the various analysis types.
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.
Is the s at the end going to cause duplicate s'es ?
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.
No, the token translates to (see elastic/docs#889):
:dataframe-analytics: {dataframe} analytics config
and "s" makes it plural
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.
Also add a section about analyzed fields
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.
Done.
Added callout in "Data Frame Analytics Configuration" section
9403dd9 to
21c5447
Compare
21c5447 to
bcec93a
Compare
|
run elasticsearch-ci/bwc |
231ebd8 to
c7fe885
Compare
dimitris-athanasiou
left a comment
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.
LGTM
c7fe885 to
85ec8a6
Compare
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.
| The index to which data should be written by the {dataframe-job}. | |
| The index to which data should be written by the {dataframe-analytics}. |
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.
Please see my other comment.
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.
{dataframe-job} again rather than {dataframe-analytics}. Is this intentional have I misunderstood the naming?
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.
It is intentional.
{dataframe-job} resolves to "data frame analytics job" and {dataframe-analytics} resolves to "data frame analytics config". So I use the former when I write about the computational process and the latter when I talk about DataFrameAnalyticsConfig.
I may rename {dataframe-analytics} to {dataframe-analytics-config} if you find it clearer. WDYT?
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.
Thanks for the explanation. I see you renamed {dataframe-analytics} to {dataframe-analytics-config} that makes sense to me
85ec8a6 to
3139167
Compare
davidkyle
left a comment
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.
LGTM
|
Pinging @elastic/es-docs (Team:Docs) |
Documentation for Data Frame Analytics high-level REST client.
Contains documentation as well as integration tests for 7 methods (Get, GetStats, Put, Delete, Start, Stop, Evaluate).
See also: elastic/docs#889