Add support to hash-field-expiration RDB_TYPE v2 #48
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.
The RDB serialization of hashes with expiration on fields (aka. HFE) was modified
to write also at the begining the minimum expiration time.
Following this change, the new value will be digested but won't be propagated to
the callback handlers since it is actually a redundant information since each field
already "reports" its expiration time to handlers (This value will might be
used in the future for optimization in the context of dumping directly
from RDB to FLUSH without parsing the object).