Skip to content

Conversation

@benwtrent
Copy link
Member

When PUT is called to store a trained model, it is useful to return the newly create model config. But, it is NOT useful to return the inflated definition.

These definitions can be large and returning the inflated definition causes undo work on the server and client side.

@elasticmachine
Copy link
Collaborator

Pinging @elastic/ml-core (:ml)

@benwtrent benwtrent requested a review from davidkyle February 20, 2020 13:35
@benwtrent benwtrent changed the title [ML][Inference] don't return inflated definition in PUT response [ML][Inference] don't return inflated definition when storing trained models Feb 20, 2020
@davidkyle
Copy link
Member

Can you add a note to the docs please. Something along the lines

The returned {response} contains the newly created model configuration with the model definition omitted as a precaution against streaming large models back in the response

Copy link
Member

@davidkyle davidkyle left a comment

Choose a reason for hiding this comment

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

LGTM

@benwtrent benwtrent merged commit 1c1d451 into elastic:master Feb 20, 2020
@benwtrent benwtrent deleted the feature/ml-inference-put-return-model branch February 20, 2020 16:25
benwtrent added a commit to benwtrent/elasticsearch that referenced this pull request Feb 20, 2020
… models (elastic#52573)

When `PUT` is called to store a trained model, it is useful to return the newly create model config. But, it is NOT useful to return the inflated definition.

These definitions can be large and returning the inflated definition causes undo work on the server and client side.
benwtrent added a commit to benwtrent/elasticsearch that referenced this pull request Feb 20, 2020
… models (elastic#52573)

When `PUT` is called to store a trained model, it is useful to return the newly create model config. But, it is NOT useful to return the inflated definition.

These definitions can be large and returning the inflated definition causes undo work on the server and client side.
benwtrent added a commit that referenced this pull request Feb 20, 2020
… models (#52573) (#52583)

When `PUT` is called to store a trained model, it is useful to return the newly create model config. But, it is NOT useful to return the inflated definition.

These definitions can be large and returning the inflated definition causes undo work on the server and client side.
benwtrent added a commit that referenced this pull request Feb 21, 2020
… models (#52573) (#52580)

When `PUT` is called to store a trained model, it is useful to return the newly create model config. But, it is NOT useful to return the inflated definition.

These definitions can be large and returning the inflated definition causes undo work on the server and client side.

Co-authored-by: Elastic Machine <[email protected]>
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