Skip to content

feat(rfc-0057): add teradata server type - #318

Merged
jgperrin merged 1 commit into
dev-v3.2.0from
rfc-0057-teradata-server-type
Aug 18, 2026
Merged

feat(rfc-0057): add teradata server type#318
jgperrin merged 1 commit into
dev-v3.2.0from
rfc-0057-teradata-server-type

Conversation

@jochenchrist

Copy link
Copy Markdown
Contributor

Applies RFC-0057 to ODCS v3.2.0: a new teradata server type for Teradata Vantage.

Fields

Key Type Required Description
host string Yes Host of the Teradata server.
port integer No Port of the Teradata server. Defaults to 1025.
database string No Name of the database.

No schema field: in Teradata, the database is the namespace.

Changes

  • Both schema files updated in lockstep (odcs-json-schema-latest.json, odcs-json-schema-v3.2.0.json): enum value, conditional dispatch, and the TeradataServer definition.
  • port uses the shared #/$defs/Port definition from RFC-0050, so it also accepts a variable reference such as ${DB_PORT}.
  • Docs section in infrastructure-servers.md, plus teradata added to the server type list.
  • Positive example docs/examples/server/teradata-server.odcs.yaml.
  • Negative test src/script/negative-tests/teradata-missing-host.odcs.yaml (missing host is rejected).
  • CHANGELOG entry.

Non-breaking: adds a new optional server type.

Validation

validate-examples.sh and validate-negative.sh pass locally against both v3.2.0 and latest. The negative test is rejected for the intended reason (must have required property 'host').

Note

The RFC still has an empty Decision section, so this needs TSC approval before merge.

Applies RFC-0057 to ODCS v3.2.0: new `teradata` server type for Teradata
Vantage. Both schema files updated in lockstep (enum value, conditional
dispatch, and TeradataServer def with required host and optional port,
defaulting to 1025, plus database). No `schema` field, since in Teradata the
database is the namespace. Port uses the shared Port $def so it accepts
variable references. Docs section, positive example, and a negative test
(missing host is rejected).
@jochenchrist
jochenchrist requested a review from a team as a code owner August 5, 2026 11:50
@jgperrin
jgperrin merged commit a3f35d1 into dev-v3.2.0 Aug 18, 2026
2 of 3 checks passed
@jgperrin
jgperrin deleted the rfc-0057-teradata-server-type branch August 18, 2026 11:14
jgperrin added a commit that referenced this pull request Aug 28, 2026
* feat(rfc-0057): add `teradata` server type (#318)

Applies RFC-0057 to ODCS v3.2.0: new `teradata` server type for Teradata
Vantage. Both schema files updated in lockstep (enum value, conditional
dispatch, and TeradataServer def with required host and optional port,
defaulting to 1025, plus database). No `schema` field, since in Teradata the
database is the namespace. Port uses the shared Port $def so it accepts
variable references. Docs section, positive example, and a negative test
(missing host is rejected).

* feat(rfc-0059): add Actian server types (#319)

Applies approved RFC-0059 to ODCS v3.2.0: four new server types — `ingres`
(Actian Ingres), `vectorwise` (Actian Analytics Engine), `versant` (Actian NoSQL
Database) and `poet` (Actian NoSQL FastObjects) — plus `fastobjects` as a
synonym of `poet` and `btrieve` as a synonym of `zen`, both dispatching to the
existing definition, as `postgresql`/`postgres` already share PostgresServer.

Both schema files updated in lockstep: enum values, conditional dispatches, and
IngresServer / VectorwiseServer / VersantServer / PoetServer defs. Ports use the
shared Port $def so they accept variable references. No `schema` field on any of
the four: for the two SQL engines the namespace is the table owner resolved from
the connecting user; the two object databases have no SQL schema namespace.

Docs sections, a positive example exercising all six values, and five negative
tests (including one per synonym, proving synonyms validate as strictly as their
primary value).


Claude-Session: https://claude.ai/code/session_01An6KmURPXG4Y8uDwd15Roq

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Jochen Christ <jochen.christ@entropy-data.com>
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants