Use new safe_to_set/safe_to_remove functions #3722
Merged
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.
safe_to_set
/safe_to_remove
functions. The new implementation will make features introduced in Don't rebuild HNSW when updating non-indexed fields #3611 and Feat/set payload by key #3548 to play well with each other.PayloadIndex::assign
by usingsafe_to_set
check here.JsonPathV2::value_remove()
idempotent by prohibiting deleting paths likea[0]
.This PR is based on #3709.
All Submissions:
dev
branch. Did you create your branch fromdev
?New Feature Submissions:
cargo +nightly fmt --all
command prior to submission?cargo clippy --all --all-features
command?Changes to Core Features: