This repository has been archived by the owner on Nov 17, 2023. It is now read-only.
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.
Opening this PR for interface review:
row_sparse_pull
python API to kvstore and c_api, which requires providingrow_id
for each row_sparsevalue
to pull. Therow_id
s are sorted in backend to contain only unique elements. The oldpull
API will not accept pulling avalue
stored in row_sparse storagekRowSparsePushPull
type to kvstore server. When received data request of this type, keys are encoded askey, row_id1, row_id2 ... row_idn
.row_sparse_pull
in regression_example.pyNote:
TODOs for next PR:
@mli @reminisce @piiswrong @madjam @stefanhenneking