Repository navigation
datastore: Support LookupResponse deferred field #77
Copy link
Copy link
Closed
Labels
🚨This issue needs some love.This issue needs some love.api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.library: cloud-profilerIssues transferred from another repositoryIssues transferred from another repositorytriage meI really want to be triaged.I really want to be triaged.
Milestone
Description
Activity
- changed the title
[-]Support LookupResponse deferred field[/-][+]datastore: Support LookupResponse deferred field[/+]on Aug 1, 2014 - added 2 commits that reference this issue
on Aug 23, 2014 Took a try at a PR: #133.
- added a commit that references this issue
on Aug 27, 2014 - added a commit that references this issue
on Aug 27, 2014 - added a commit that references this issue
on Aug 27, 2014 - addedapi: datastoreIssues related to the Datastore API.Issues related to the Datastore API.
on Feb 2, 2015 - added🚨This issue needs some love.This issue needs some love.triage meI really want to be triaged.I really want to be triaged.
on Apr 6, 2020 70 remaining items
- added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Mar 5, 2026 - added 2 commits that reference this issue
on Mar 9, 2026 - added 2 commits that reference this issue
on Mar 23, 2026 - added a commit that references this issue
on May 5, 2026
Metadata
Metadata
Assignees
Labels
🚨This issue needs some love.This issue needs some love.api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.library: cloud-profilerIssues transferred from another repositoryIssues transferred from another repositorytriage meI really want to be triaged.I really want to be triaged.
When a LookupRequest is made, the response may contain keys in the deferred field that were not able to be answered due to resource/time constraints.
getAll should probably either expose this to the user or fire off another request for the rest of the keys.