Investigate Amazon Redshift support (provisioned and serverless)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 25/100
Direzione di ricerca
Start by reading the existing grate.postgresql provider and its tests, then compare its connection, history, catalog, locking, and transaction assumptions with the Redshift behaviors named in the proposal. Evaluate provisioned and Serverless connectivity, including the Data API option, and record a provider and execution design with supported scope and limitations. Done means a documented decision and a real-target test plan for bootstrap, schema changes, reruns, failures, and concurrency.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
Investigate adding Amazon Redshift as a migration target in grate, covering both provisioned clusters and Redshift Serverless. Determine whether it can be supported safely by adapting grate.postgresql or whether it requires a dedicated grate.redshift provider. Also evaluate an optional AWS Redshift Data API execution transport, analogous to the job-based approach proposed for BigQuery in #829.
This is a proposal for discussion rather than a commitment to a specific provider architecture.
Motivation
Redshift is an analytical data warehouse whose SQL syntax and protocol have PostgreSQL roots, but its DDL capabilities, catalog metadata, and operational behavior differ materially from PostgreSQL. Teams may want the same versioned, auditable database changes and script-folder conventions they use with grate for other systems, without assuming PostgreSQL compatibility where it is not guaranteed.
Potential migration use cases include creating and evolving schemas, tables, views, materialized views, and other supported Redshift database objects, plus controlled data transformations.
Proposed discovery / initial scope
- Compare the existing
grate.postgresqlprovider's bootstrapping, history tables, catalog queries, syntax, locking, and transaction behavior against Redshift. - Validate direct PostgreSQL-protocol connectivity and authentication against both provisioned and Serverless endpoints.
- Evaluate an alternative AWS SDK/.NET-based Redshift Data API transport using
ExecuteStatement/DescribeStatementand, where useful,BatchExecuteStatement; assess how asynchronous execution, sessions, idempotency tokens, and cancellation map to grate'sIDatabasecontract. - Determine the correct handling for one-time, anytime, every-time, and environment scripts, including script splitting and error reporting.
- Persist migration history and failure details in a dedicated schema or otherwise appropriate Redshift objects; verify permissions and concurrent migration behavior.
- Verify DDL transaction behavior per operation rather than assuming PostgreSQL semantics; define recovery rules for partially applied scripts.
- Document prerequisites, IAM/Secrets Manager or database authentication options, configuration, and costs.
- Add integration tests against real Redshift Provisioned and Serverless targets, with credentials supplied securely by the test environment.
Design questions
- Is a compatibility layer on top of
grate.postgresqlsufficient, or are there enough differences to justifygrate.redshift? - Should a Redshift Data API transport be a separate provider, an optional execution backend, or a later enhancement?
- Which DDL commands are transactional, and how should grate handle commands requiring execution outside an explicit transaction?
- What history-table/locking strategy avoids concurrent runners applying the same change?
- How should asynchronous requests be resumed or reconciled after a timeout or client crash, avoiding duplicate execution?
- Which objects and features should the first version support (internal schemas/tables/views only versus external schemas, Spectrum, datashares, materialized views, etc.)?
- How would a Redshift implementation fit with a proposed separation of migration targets, execution transports, and database semantics?
Suggested acceptance criteria for an initial implementation
- A documented decision is made on PostgreSQL provider reuse versus a dedicated Redshift provider.
- The basic test workflow runs against at least one real Redshift target: bootstrap history, apply initial table DDL, apply a second schema change, and re-run without repeating successful one-time scripts.
- Failures, partial application, retries, and concurrency are handled or explicitly documented as limitations.
- At least provisioned and Serverless connectivity are evaluated; unsupported modes are clearly documented.
- Provider-specific differences from PostgreSQL are covered by tests and documentation.
Non-goals (initial)
- Provisioning Redshift clusters/workgroups or managing infrastructure as code.
- Migrating data stored in S3 directly or managing AWS Glue catalogs independently of a Redshift execution target.
- Assuming generic PostgreSQL DDL or transactional behavior is automatically valid for Redshift.
- Supporting every Redshift administrative object in the first iteration.
Related work
- BigQuery provider proposal: #829
- Fabric Lakehouse provider proposal: #885
- AWS documentation: Amazon Redshift and PostgreSQL
- AWS documentation: Using the Amazon Redshift Data API
- AWS documentation: ExecuteStatement API
Discussion proposal: validate the smallest useful integration before deciding on a new NuGet provider package.
- Lingua principale
- C#
- Stelle
- 305
- Fork
- 59
- Merge medio
- 1g 27m
- PR unite (30g)
- 79
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di grate-devs/grate
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
grate-devs/grate#969 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 30/100
grate-devs/grate#971 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 42/100
grate-devs/grate#970 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
grate-devs/grate#967 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 30/100
grate-devs/grate#956 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di grate-devs/grate
Issue simili
-
CLI: stale build hint, non-gofmt autocomplete output and a leftover `--revit=<year>` in the docsApertaCommand Line Utility (CLI)
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
pyrevitlabs/pyRevit#4217 ·
I maintainer di solito rispondono entro 1 giorno
-
account bug effort:S P2
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
nightscout/nocturne#3745 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
modelcontextprotocol/csharp-sdk#2031 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
jsboige/CoursIA#27768 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
I maintainer di solito rispondono entro 1 giorno