Skip to content

Conversation

@vladimirdolzhenko
Copy link
Contributor

adds support of /_xpack/ml/info endpoint to get ML info (defaults)

Note: the reason for WIP: there is no docs for this API

Relates to #29827

droberts195 pushed a commit to droberts195/elasticsearch that referenced this pull request Nov 21, 2018
This endpoint was not previously documented as it was not
particularly useful to end users.  However, since the HLRC
will support the endpoint we need some documentation to
link to.

The purpose of the endpoint is to provide defaults and
limits used by ML.  These are needed to fully understand
configurations that have missing values because the missing
value means the default should be used.

Relates elastic#35777
@droberts195
Copy link

#35783 adds some docs for the REST endpoint.

@vladimirdolzhenko vladimirdolzhenko changed the title [WIP][HLRC] XPack ML info action [HLRC] XPack ML info action Nov 21, 2018
droberts195 pushed a commit that referenced this pull request Nov 22, 2018
This endpoint was not previously documented as it was not
particularly useful to end users.  However, since the HLRC
will support the endpoint we need some documentation to
link to.

The purpose of the endpoint is to provide defaults and
limits used by ML.  These are needed to fully understand
configurations that have missing values because the missing
value means the default should be used.

Relates #35777
droberts195 pushed a commit that referenced this pull request Nov 22, 2018
This endpoint was not previously documented as it was not
particularly useful to end users.  However, since the HLRC
will support the endpoint we need some documentation to
link to.

The purpose of the endpoint is to provide defaults and
limits used by ML.  These are needed to fully understand
configurations that have missing values because the missing
value means the default should be used.

Relates #35777
droberts195 pushed a commit that referenced this pull request Nov 22, 2018
This endpoint was not previously documented as it was not
particularly useful to end users.  However, since the HLRC
will support the endpoint we need some documentation to
link to.

The purpose of the endpoint is to provide defaults and
limits used by ML.  These are needed to fully understand
configurations that have missing values because the missing
value means the default should be used.

Relates #35777
@droberts195
Copy link

@vladimirdolzhenko
Copy link
Contributor Author

@droberts195 thank you

original-brownbear pushed a commit that referenced this pull request Nov 23, 2018
This endpoint was not previously documented as it was not
particularly useful to end users.  However, since the HLRC
will support the endpoint we need some documentation to
link to.

The purpose of the endpoint is to provide defaults and
limits used by ML.  These are needed to fully understand
configurations that have missing values because the missing
value means the default should be used.

Relates #35777
Copy link
Contributor

@hub-cap hub-cap left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

small question on the response object, but the rest LGTM. Once I have clarity there we can :shipit:

@droberts195 droberts195 self-assigned this Nov 27, 2018
@droberts195 droberts195 merged commit f0c5f0c into elastic:master Nov 28, 2018
droberts195 pushed a commit that referenced this pull request Nov 28, 2018
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.

4 participants