You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use BigtableToAvro to backup a huge Bigtable in production.
We have a replication on the BigTable. The main application connects to the Bigtable on one of the regions.
We want to force the backup process (BigtableToAvro) to use a specific Bigtable instance, which is in another region.
The reason is we don't want to affect the main application performance.
This feature already exists in Cloud Bigtable to Cloud Storage SequenceFile
The text was updated successfully, but these errors were encountered:
This issue has been marked as stale due to 180 days of inactivity. It will be closed in 1 week if no further activity occurs. If you think that’s incorrect or this pull request requires a review, please simply write any comment. If closed, you can revive the issue at any time. Thank you for your contributions.
This issue has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.
We use BigtableToAvro to backup a huge Bigtable in production.
We have a replication on the BigTable. The main application connects to the Bigtable on one of the regions.
We want to force the backup process (BigtableToAvro) to use a specific Bigtable instance, which is in another region.
The reason is we don't want to affect the main application performance.
This feature already exists in Cloud Bigtable to Cloud Storage SequenceFile
The text was updated successfully, but these errors were encountered: