Rename guid in liveliness_utils to keyexpr_hash. #296
Closed
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.
This more clearly reflect what it is, which is a
hash of the keyexpression that is used to index into various maps.
FYI @ahcorde and @Yadunund . I think this more accurately reflects what this particular data is used for, and helps (at least in my mind) to clear up some confusion about the "real" GID that we need to return from get_entities_info_by_topic.
Going forward, what I think we should do is the following:
What do you think? Does that make sense?