Don't request null keys from KVStore #774
Open
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.
Summary
Updates the Fetcher to not include or attempt any requests when the keys are null.
Why / Goal
KVStore implementations are left up to consumers. In the case where null entries are being written out, this can lead to online/offline consistency issues. The GroupByUpload jobs are all setup to filter out any null keys, but the KVStore will still attempt to pull values if they exist. This adds parity with the null checks done in the GroupByUpload jobs to the online path and will exclude any attempt to pull values for null keys.
Test Plan
Checklist
Reviewers