Skip to content

fix(geminidataanalytics)!: generate and default to v1#17007

Open
noahdietz wants to merge 1 commit intogoogleapis:mainfrom
noahdietz:onboard-new-library-2026-05-08
Open

fix(geminidataanalytics)!: generate and default to v1#17007
noahdietz wants to merge 1 commit intogoogleapis:mainfrom
noahdietz:onboard-new-library-2026-05-08

Conversation

@noahdietz
Copy link
Copy Markdown
Contributor

Adds v1 to existing google-cloud-geminidataanalytics client and switches default_version to v1.

Towards b/510217868

@noahdietz noahdietz requested review from a team as code owners May 8, 2026 17:06
@snippet-bot
Copy link
Copy Markdown

snippet-bot Bot commented May 8, 2026

Here is the summary of changes.

You are about to add 34 region tags.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request promotes the Gemini Data Analytics API client library to v1, replacing v1alpha as the default version. The update encompasses comprehensive changes across library configuration, metadata, and documentation, alongside the complete implementation of v1 services, transports, and types. Feedback from the review identifies several documentation improvements needed in datasource.py, specifically addressing an inconsistency in the BigQueryTableReferences docstring, removing internal proto path references, and fixing a truncated attribute description.

Comment on lines +107 to +110
r"""Message representing references to BigQuery tables and property
graphs. At least one of ``table_references``,
``property_graph_references``, or ``search_scope`` must be
populated.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The docstring for BigQueryTableReferences states that at least one of table_references, property_graph_references, or search_scope must be populated. However, the message definition only includes table_references. Ensure the docstring accurately reflects the implementation, even if other documentation sources (like proto files) are inconsistent.

References
  1. Ensure docstrings reflect logic correctly, even if other documentation sources (like proto files) are inconsistent.

Comment on lines +441 to +443
Optional. Table display_name (same as label in
cloud/data_analytics/anarres/data/looker/proto/model_explore.proto),
not required, currently only Looker has this field.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The docstring for display_name in the Schema message contains a reference to an internal Google proto path (cloud/data_analytics/anarres/data/looker/proto/model_explore.proto). This internal detail should be removed from the public API documentation to maintain clarity and professionalism.

Suggested change
Optional. Table display_name (same as label in
cloud/data_analytics/anarres/data/looker/proto/model_explore.proto),
not required, currently only Looker has this field.
Optional. Table display_name, not required, currently only Looker has this field.

sources.
display_name (str):
Optional. Field display_name (same as label in
subfields (MutableSequence[google.cloud.geminidataanalytics_v1.types.Field]):
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The docstring for the display_name attribute in the Field message is truncated and ends abruptly. It should be completed to provide full context to the user.

@daniel-sanche daniel-sanche changed the title feat(geminidataanalytics): generate and default to v1 feat(geminidataanalytics)!: generate and default to v1 May 8, 2026
@daniel-sanche daniel-sanche added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label May 8, 2026
@daniel-sanche
Copy link
Copy Markdown
Contributor

I added a ! to the title, since I believe this should be a breaking change. I'm going to come back and look at this soon to be sure though

@daniel-sanche daniel-sanche removed the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label May 8, 2026
@daniel-sanche daniel-sanche changed the title feat(geminidataanalytics)!: generate and default to v1 feat(geminidataanalytics): generate and default to v1 May 8, 2026
@daniel-sanche
Copy link
Copy Markdown
Contributor

Removed !, because this library is in previous, so we can update the default without a major update

Copy link
Copy Markdown
Contributor

@daniel-sanche daniel-sanche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@daniel-sanche daniel-sanche changed the title feat(geminidataanalytics): generate and default to v1 fix(geminidataanalytics)!: generate and default to v1 May 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants