Skip to content
This repository was archived by the owner on Aug 30, 2026. It is now read-only.
This repository was archived by the owner on Aug 30, 2026. It is now read-only.

Review exception structure #794

Closed
Closed

Description

@daniel-sanche

For the v3 client, we use exception groups to group a sequence of retry exceptions, and also to group exceptions related to a bulk operation. In some cases, these groups can be nested, with retry groups inside of bulk operation exception groups.

We should review how we want to expose this, to make sure handling exceptions is user-friendly, and root causes are easy to determine.

Discussion here: #769 (comment)


We also have to make sure our exceptions follow the actionable error conventions, and that error details are properly exposed in error messages


ExceptionGroups should print some (or all) of the sub-exceptions for debugging, even on < 3.11

Activity

  1. added
    type: cleanupAn internal cleanup or hygiene concern.
    priority: p3Desirable enhancement or fix. May not be included in next release.
    on Jun 5, 2023
  2. added this to the v3 milestone on Jun 5, 2023
  3. self-assigned this
    on Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: bigtableIssues related to the googleapis/python-bigtable API.priority: p3Desirable enhancement or fix. May not be included in next release.type: cleanupAn internal cleanup or hygiene concern.

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions