Skip to content

datastore: Support LookupResponse deferred field #77

Description

@pcostell

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.

Activity

  1. changed the title [-]Support LookupResponse deferred field[/-] [+]datastore: Support LookupResponse deferred field[/+] on Aug 1, 2014
  2. added this to the milestone on Aug 5, 2014
  3. added 2 commits that reference this issue on Aug 23, 2014
    53db768
    ceb8122
  4. stephenplusplus commented on Aug 23, 2014

    @stephenplusplus
    Contributor

    Took a try at a PR: #133.

  5. added a commit that references this issue on Aug 27, 2014
    473f55d
  6. added a commit that references this issue on Aug 27, 2014
    72752dd
  7. added a commit that references this issue on Aug 27, 2014
    610e478
  8. modified the milestones: Datastore Stable, on Feb 2, 2015
  9. 70 remaining items

  10. added a commit that references this issue on Mar 27, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

🚨This issue needs some love.api: datastoreIssues related to the Datastore API.library: cloud-profilerIssues transferred from another repositorytriage meI really want to be triaged.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions