Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Proposal]: use upstream bigquery/storage/managedwriter package instead of our forked version #4

Closed
1 task done
GlenDC opened this issue Nov 5, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@GlenDC
Copy link
Member

GlenDC commented Nov 5, 2021

Contact Details

No response

Summary of your proposal

Use the upstream bigquery/storage/managedwriter package instead of our forked version.
One of the issues that ideally is resolved prior to doing so is googleapis/google-cloud-go#5094.

Motivation for your proposal

The main motivation is that we have less code to maintain ourselves.

Alternatives for your proposal

The alternative is to either not use a managedWriter in which case we're going to reinvent the wheel most likely. The only other obvious option is to continue using our fork but that means we'll also need to maintain it ourselves, and do so mostly alone.

Version

0.3.1 (Latest)

What platform are you mostly using or planning to use our software on?

MacOS

Code of Conduct

  • I agree to follow this project's Code of Conduct
@GlenDC GlenDC added the enhancement New feature or request label Nov 5, 2021
@GlenDC GlenDC changed the title [Proposal]: [Proposal]: use upstream bigquery/storage/managedwriter package instead of our forked version Nov 5, 2021
@GlenDC
Copy link
Member Author

GlenDC commented Nov 9, 2021

Resolved in #6.

@GlenDC GlenDC closed this as completed Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant