atlan-sql-connector-patterns

SQL connector patterns depend on your source requirements. Postgres-minimal uses SDK defaults for standard SQL sources, while redshift-custom implements source-specific logic. Choose redshift-custom only when your SQL source requires custom authentication, preflight checks, or transformation behavior beyond the SDK baseline.

Implementation requires selecting your pattern, documenting the rationale, verifying authentication and preflight checks, mapping workflow components, defining transformations, and running contract validators. This ensures your connector adheres to SDK standards and handles your source correctly.

Use a custom connector when your SQL source has specialized requirements: non-standard authentication, custom preflight validation, source-specific query transformations, or unique metadata extraction logic. The minimal pattern works for standard Postgres-compatible sources without these requirements.

Yes. SQL connector patterns guide selection and implementation for adding new SQL sources—whether databases like Postgres, Redshift, or others. Document your pattern choice, implement required components, and validate behavior against reference specifications and contract validators.

Failed authentication or preflight checks indicate your connector configuration or source environment needs adjustment. The pattern requires documenting and verifying these checks before proceeding. Contract validators catch misconfigurations early, preventing metadata extraction failures downstream.

Verify by running contract validators against your connector, testing transformation behavior against reference maps, and confirming preflight checks and authentication succeed. These validation steps ensure your chosen pattern meets SDK standards and your source integrates correctly.