Repository navigation
Add a clearer resolution to #294 (or remove from the docs?) #590
Copy link
Copy link
Closed
Labels
api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.
Milestone
Description
Activity
- addedapi: datastoreIssues related to the Datastore API.Issues related to the Datastore API.
on May 12, 2015 - changed the title
[-]Add a clearer resolution to #294[/-][+]Add a clearer resolution to #294 (or remove from the docs?)[/+]on May 12, 2015 - added a commit that references this issue
on Sep 13, 2023 - added a commit that references this issue
on Jul 23, 2025 - added a commit that references this issue
on Jan 28, 2026 - added a commit that references this issue
on Feb 5, 2026 - added a commit that references this issue
on Feb 17, 2026 - added a commit that references this issue
on Feb 23, 2026 - added 2 commits that reference this issue
on Feb 24, 2026 - added a commit that references this issue
on Feb 26, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 18, 2026
Metadata
Metadata
Assignees
Labels
api: datastoreIssues related to the Datastore API.Issues related to the Datastore API.
We link to #294 in our docs for a particular error, but I can't see the correct resolution there -- it doesn't seem obvious to me what I have to do to get this to work, or what the underlying problem was.
For reference, on gcloud-python, we had a similar issue, and it was due to the Project ID vs Dataset ID distinction not being clear (the user was setting the project ID correctly, but not setting the Dataset ID correctly -- and they should be the same).
Can we add a comment saying "BTW, the issue here was X and the way to fix this in the future is to do Y" ?