Standardized GET (TENSORGET,MODELGET,SCRIPTGET) methods replies (breaking change for clients) #332
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Addresses #329
Specifically, with this PR, get methods have a uniform signature and behavior
If META is not specified, all methods return a raw binary BLOB, an array VALUES or a raw SOURCE string. This helps, for instance, with dumping a buffer out of a model or a tensor from the CLI.
If only META is specified, all methods return meta data in [key, val, key, val] form. This is a breaking change with respect to the previous behavior (TENSORGET would return [dtype, shape, blob] and not ['dtype', dtype, 'shape', shape, 'blob', blob]), so THIS CHANGE WILL BREAK CLIENTS AND USER CODE.
However, this is our last call to make the API uniform and ready for RESP3.
Other notable changes:
AI.INFO
)_MODELLIST
command has been renamed to_MODELSCAN
(to prepare for the upcomingTENSORLIST
data type)Tests and docs have been updated.