Skip to content

populate "force" in allocateId requests once datasore api expose it. #16

Closed

Description

@aozarov

see b/18594027

Activity

  1. aozarov commented on Oct 23, 2015

    @aozarov
    ContributorAuthor

    I think we can close that as Datastore v1beta3 seems to remove "force" completely.
    Is that right @ajkannan ?

  2. ajkannan commented on Oct 23, 2015

    @ajkannan

    Yup, they've removed force completely. In my understanding, it could be added back in the future, but that's unclear. We can reopen this issue if it ever does get added back.

  3. added a commit that references this issue on Mar 29, 2016
  4. added 3 commits that reference this issue on Feb 24, 2026
  5. added 3 commits that reference this issue on Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

🚨 criticalP0 critical issue. Requires immediate fixapi: datastoreIssues related to the Datastore API.triage meI really want to be triaged.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions