Skip to content

v3: use defaults for inclusive flags #15316

Open
Open
v3: use defaults for inclusive flags#15316
Assignees
daniel-sanche
Labels
api: bigtableIssues related to the Bigtable API.priority: p3Desirable enhancement or fix. May not be included in next release.type: cleanupAn internal cleanup or hygiene concern.

Description

@daniel-sanche
daniel-sanche
opened on Jun 29, 2023

We currently use None to for inclusive flags, and raise an error if the flag is set when the field is not. WE have this behaviour in both RowRange and RowFilter.

We should consider using default values in the signature instead, to make things simpler

Context: googleapis/python-bigtable#820 (comment)

Activity

  1. daniel-sanche
    added
    type: cleanupAn internal cleanup or hygiene concern.
    priority: p3Desirable enhancement or fix. May not be included in next release.
    on Jun 29, 2023
  2. daniel-sanche
    self-assigned this
    on Jun 29, 2023
  3. product-auto-label
    added
    api: bigtableIssues related to the Bigtable API.
    on Jun 29, 2023

  4. parthea commented on Jan 12, 2026

    @parthea
    parthea
    on Jan 12, 2026
    Contributor

    Transferring to google-cloud-python as the code for python-bigtable will be migrated there in 1-3 weeks.

  5. parthea
    transferred this issue fromgoogleapis/python-bigtableon Jan 12, 2026
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 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

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions