Skip to content

Clarify limited write access in BigQuery docs#12840

Merged
martint merged 1 commit intotrinodb:masterfrom
colebow:colebow/bigquery-docs
Jun 22, 2022
Merged

Clarify limited write access in BigQuery docs#12840
martint merged 1 commit intotrinodb:masterfrom
colebow:colebow/bigquery-docs

Conversation

@colebow
Copy link
Copy Markdown
Member

@colebow colebow commented Jun 14, 2022

Description

Updating docs to remove inaccurate info

Is this change a fix, improvement, new feature, refactoring, or other?

Improvement

Is this a change to the core query engine, a connector, client library, or the SPI interfaces? (be specific)

Docs only

Related issues, pull requests, and links

Documentation

( ) No documentation is needed.
(x) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.

Release notes

(x) No release notes entries required.
( ) Release notes entries required with the following suggested text:

@cla-bot cla-bot bot added the cla-signed label Jun 14, 2022
@github-actions github-actions bot added the docs label Jun 14, 2022
@colebow colebow requested review from ebyhr and mosabua June 14, 2022 17:29
Copy link
Copy Markdown
Member

@hashhar hashhar left a comment

Choose a reason for hiding this comment

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

We should be consistent and do what we have done in other connectors. i.e. mention both read and write in the paragraph and enumerate the specific ones that are supported in the bullet list.

e.g. https://github.com/trinodb/trino/blob/master/docs/src/main/sphinx/connector/sqlserver.rst#sql-support

@colebow
Copy link
Copy Markdown
Member Author

colebow commented Jun 15, 2022

Would it reasonable to include a "but write access is limited" or something like that to emphasize that you're only able to create tables/schemas?

@colebow colebow force-pushed the colebow/bigquery-docs branch from 39a0e79 to e8942fd Compare June 16, 2022 16:23
@colebow colebow requested review from hashhar, martint and mosabua June 16, 2022 20:57
Copy link
Copy Markdown
Member

@mosabua mosabua left a comment

Choose a reason for hiding this comment

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

I am okay with this change for now. What we really should do is expand the write support and then get rid of this hedging that its limited again.

Copy link
Copy Markdown
Member

@ebyhr ebyhr left a comment

Choose a reason for hiding this comment

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

Please fix commit message. The latest change is not "Remove inaccurate mention of write access"

@colebow colebow force-pushed the colebow/bigquery-docs branch from e8942fd to 8579cbd Compare June 17, 2022 16:43
@colebow colebow changed the title Remove inaccurate mention of write access in BigQuery docs Clarify limited write access in BigQuery docs Jun 22, 2022
@martint martint merged commit db70c4d into trinodb:master Jun 22, 2022
@github-actions github-actions bot added this to the 387 milestone Jun 22, 2022
@colebow colebow deleted the colebow/bigquery-docs branch September 8, 2022 18:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Development

Successfully merging this pull request may close these issues.

5 participants