feat(rfc-0058): add exasol server type - #313
Merged
Merged
Conversation
Applies approved RFC-0058 to ODCS v3.2.0: new `exasol` server type for Exasol, an in-memory MPP analytics database. Both schema files updated in lockstep — enum value, conditional dispatch, and ExasolServer def with required host and optional port (default 8563) + schema. No `database` field: an Exasol cluster runs a single database and the schema is the namespace. Docs section, positive example, and a negative test (missing host -> rejected). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Applies RFC-0058 — Exasol server type (champion: Jochen Christ, approved by the TSC 2026-08-05) to ODCS v3.2.0.
Exasol is an in-memory MPP analytics database used as an enterprise data warehouse. Until now users had to fall back on
custom, losing structured, validatable connection metadata.Field shape (per the RFC field table)
typeexasolhostn11..14.acme.comport8563schemaNo
databasefield — an Exasol cluster runs a single database and the schema is the namespace.Changes
CHANGELOG.md— entry under v3.2.0 (IN PROGRESS), linking the approved RFCschema/odcs-json-schema-latest.jsonandschema/odcs-json-schema-v3.2.0.json— updated in lockstep:exasolenum value,if/thendispatch, and theExasolServerdef (required: [host],portvia$defs/Portso RFC-0050 variable references keep working)docs/infrastructure-servers.md— new Exasol section +exasoladded to thetypevalue listdocs/examples/server/exasol-server.odcs.yaml— positive examplesrc/script/negative-tests/exasol-missing-host.odcs.yaml— negative test:hostomittedValidation
src/script/validate-examples.sh→ exit 0,Total failed=0; the new example validatessrc/script/validate-negative.sh→ exit 0,Total failed=0; the new fixture is rejected withmust have required property 'host'Non-breaking: adds a new optional server type.
🤖 Generated with Claude Code