Skip to main content

Hydra-Ext

Extension coders for Hydra: schema languages and data formats outside the core hydra-pg / hydra-rdf set. This package holds DSL sources only — generated output lands under dist/<lang>/hydra-ext/ for each target language that the package supports.

Hydra is a functional programming language based on the LambdaGraph data model. See the main Hydra README for project overview and use cases.

What's in this package

Coders, syntax models, and language metadata for:

  • Schema languages and IDLs — Avro, Protobuf, GraphQL, Pegasus/PDL, JSON Schema, YAML, SQL (ANSI), Datalog, Kusto KQL.
  • Generation targets — C++, C# (Csharp), Rust.
  • Domain models — Workflow, Atlas, Azure DTDL, GeoJSON, IANA Relations, OSV (Open Source Vulnerability), STAC Items, Parquet/Delta Parquet.

The full list is maintained in src/main/haskell/Hydra/Sources/Ext/Manifest.hs.

Not in this package

A few originally-Ext members have moved out into their own packages as they matured into proper coders:

Sync scope

hydra-ext is not part of the default bin/sync.sh host × target matrix. Most modules here are experimental schema and syntax models rather than full cross-language coders. The package's package.json declares:

"targetLanguages": ["python"]

which scopes regeneration to Python-side artifacts under dist/python/hydra-ext/. To regenerate, run from a worktree root:

bin/sync.sh --hosts haskell --targets python    # via the kernel manifest

The Haskell-side DSL sources are processed in Phase 1 of every bin/sync.sh invocation; the result lands in dist/json/hydra-ext/. Target-language emission beyond Python is currently opt-in and limited.

Demos using hydra-ext

Several demos exercise extension coders:

  • Avro demo — bidirectional Avro schema reading and writing.
  • GenPG demo — CSV → property graph (uses Avro for schemas).
  • GraphQL JSON demo — GraphQL schema inference and JSON validation.
  • SHACL demo — uses several ext models.

Adding a coder

For a new schema language or generation target:

  1. Add the DSL source modules under src/main/haskell/Hydra/Sources/<Lang>/ (Coder.hs, Language.hs, Serde.hs, Syntax.hs at minimum).
  2. Register them in src/main/haskell/Hydra/Sources/Ext/Manifest.hs's mainModules list.
  3. Run heads/haskell/bin/sync-haskell.sh to regenerate the JSON kernel and validate that the new sources type-check against the rest of hydra-ext.

For the broader process, see Creating a new Hydra implementation (for full host languages) or Adding new primitives (for new functions in hydra.lib.*).

See also

Metadata

Release files for hydra-ext 0.18.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for hydra-ext 0.18.0
File Size Uploaded Provenance Actions
hydra_ext-0.18.0.tar.gz 426.3 kB Without provenance Details for hydra_ext-0.18.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for hydra-ext 0.18.0
File Interpreter ABI Platform Actions
hydra_ext-0.18.0-py3-none-any.whl Python 3 none any Details for hydra_ext-0.18.0-py3-none-any.whl

Total release size: 878.8 kB

Release files / hydra_ext-0.18.0.tar.gz

Download URL hydra_ext-0.18.0.tar.gz
Size 426.3 kB
Tags Source
SHA-256 checksum
How to use checksums
88f6c0aa36360c4b6e6cbfe1fa0e9ccf0e8620871ea8abf59dd5fa7c5e2f14e4
BLAKE2b-256 checksum
How to use checksums
fadf60b5fd83a2c4243ac740614715e4da00ae7eb413051183db752cfc2968ac
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Release files / hydra_ext-0.18.0-py3-none-any.whl

Download URL hydra_ext-0.18.0-py3-none-any.whl
Size 452.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
49f0d7e586daf8b9fbada3d738a99888bf8a3ff3a138b51df89f7244c1518224
BLAKE2b-256 checksum
How to use checksums
cc5d8019b63c1b851f192b8b685b9f53a4ca39b1071ae7fd276e65335d1f29da
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.12.8

Security for hydra-ext 0.18.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page