Skip to content

Make DatastoreException message more informative #478

Closed

Description

@ajkannan

In DefaultDatastoreRpc.translate(DatastoreException exception), we lose helpful error messages because we only throw a DatastoreRpcException based on the associated Reason. For example, in a malformed query request, the user gets an exception with the message "Invalid request". The original exception thrown and translated by the method mentioned above may include a message such as "must specify all group by orderings before any non group by orderings", which is far more helpful for the user.

Activity

  1. aozarov commented on Dec 17, 2015

    @aozarov
    Contributor

    👍 Could be handled by #438.

  2. aozarov commented on Jan 11, 2016

    @aozarov
    Contributor

    We could also set root cause to the original exception (should be useful even after #438).

  3. added 4 commits that reference this issue on Jan 11, 2016
    8760be1
    25ad65f
    04d8eef
    1583312
  4. added a commit that references this issue on Jan 12, 2016
    b62017c
  5. 3 remaining items

  6. added a commit that references this issue on Oct 5, 2022
  7. added a commit that references this issue on Dec 22, 2025
  8. added a commit that references this issue on Jan 22, 2026
  9. added a commit that references this issue on Jul 13, 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: coreapi: 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

    Sponsor
    SponsoredKunjungi sekarang
    Promo