Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Add Python sample for restoring multiple deleted BigQuery tables concurrently

Aperta
  • Qualcosa non va?
#14,641 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

@alihanoz-google ci sta già lavorando.

Dal 13/10/2026.

  • #14642 di @alihanoz-google — aperta

Valutazione

Difficoltà
3/5
Tempo stimato
Mezza giornata
Idoneità per principianti
15/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Ferma
Stack tecnologico
gcp, python
Ambito
databases

Direzione di ricerca

The work is a Python sample that queries INFORMATION_SCHEMA.TABLE_STORAGE for recently deleted tables, computes time-travel timestamps, and restores them concurrently with a ThreadPoolExecutor. Pull request #14642 is already open against this issue, so review or coordinate on that PR rather than starting a parallel implementation. Done means the sample runs against a test dataset and restores the tables to the destination dataset.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

priority: p3 samples triage me type: feature request

Is your feature request related to a problem? Please describe.

Yes. Customers often need to restore multiple deleted BigQuery tables at once (e.g., after an accidental bulk deletion or dropping a dataset). Currently, the public documentation only provides examples for restoring a single table at a time, leaving users to figure out how to write their own concurrent restoration logic using time travel decorators and the INFORMATION_SCHEMA.

Describe the solution you'd like.

Add a Python sample script demonstrating how to programmatically query INFORMATION_SCHEMA.TABLE_STORAGE to find all recently deleted tables in a dataset, calculate their time travel timestamps, and restore them concurrently to a new destination dataset using the BigQuery Python client and a ThreadPoolExecutor.

This sample will be surfaced in the public BigQuery documentation via an include tag to help customers perform bulk restorations.

Describe alternatives you've considered.

The alternative is requiring users to manually restore tables one-by-one via the bq CLI or write their own custom bulk-restore scripts from scratch, which is error-prone and tedious for large datasets.

Additional context.

This sample was explicitly requested by the BigQuery tech writing team to be surfaced in the public documentation for recovering deleted tables (Internal tracking: cl/998554059, b/533404964).

I already have the code prepared and will open a Pull Request linking to this issue shortly!

Lingua principale
Jupyter Notebook
Stelle
8.1k
Fork
6.7k
Merge medio
3g 11h
PR unite (30g)
12

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di GoogleCloudPlatform/python-docs-samples

Tutte le issue di GoogleCloudPlatform/python-docs-samples

Issue simili

Altre issue su Databases

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.