fluid odps-bitol
Export FLUID contracts to and validate Bitol.io's ODPS (Open Data Product Standard) v1.0 format, used for marketplace integrations such as Entropy Data.
Use fluid odps for new workflows
Since v0.8.4, the unified fluid odps command dispatches between Bitol 1.0.0 and LF/ODPI 4.1 via --spec, and adds an import subcommand. fluid odps-bitol remains for backward compatibility and more explicit Bitol-only workflows.
Syntax
fluid odps-bitol export CONTRACT [--output PATH] [--format FMT] [--no-custom] [--api-version VER]
fluid odps-bitol validate ODPS_FILE
fluid odps-bitol info
Key options
odps-bitol export
| Option | Description |
|---|---|
CONTRACT | Path to FLUID contract file. |
--output, -o | Output file path. Default: the contract file's name without its last extension, plus -odps and the format. contract.fluid.yaml writes contract.fluid-odps.yaml. |
--format, -f | Output format: yaml or json. Default yaml. |
--no-custom | Exclude custom properties from the output. |
--api-version | ODPS apiVersion to emit: v1.0.0 or v1.1.0. Both are released Bitol standards. v1.1.0 (RFC 0029, released 2026-09-08) adds the top-level type — sourceAligned / aggregate / consumerAligned, mapped 1:1 and bidirectionally to FLUID SDP / ADP / CDP (metadata.productType) — and forge-cli has emitted it on request since v0.13.1. v1.0.0 stays the default: the emitted apiVersion is what every existing consumer parses, so the default moves with a schema bump rather than silently. The ODPS_API_VERSION env var sets the default. |
odps-bitol validate
| Option | Description |
|---|---|
ODPS_FILE | Path to an ODPS-Bitol data product file. |
odps-bitol info
No options. Prints exporter information (version, spec URL, capabilities).
Examples
fluid odps-bitol export contract.fluid.yaml
fluid odps-bitol export contract.fluid.yaml -o product.json -f json
fluid odps-bitol export contract.fluid.yaml --api-version v1.1.0
fluid odps-bitol validate product.yaml
fluid odps-bitol info
Unified fluid odps (since v0.8.3)
The unified fluid odps command dispatches between Bitol 1.0.0 and LF/ODPI 4.1 via --spec, and adds an import subcommand:
fluid odps export <contract> [--spec bitol-1.0.0|odps-4.1] [--out PATH] [--out-dir DIR]
fluid odps import <path> [--spec bitol-1.0.0] [--allow-remote] [-o PATH]
fluid odps validate <file> [--spec ...]
fluid odps info [--spec ...]
fluid odps import accepts three entry shapes — single ODPS doc, directory bundle (ODPS + sibling ODCS files), or a lone ODCS file. Remote contractId references are off by default; opt in with --allow-remote (SSRF-guarded — see network safety).
--spec rename in v0.8.4
--spec odpi-4.1 (the old LF/ODPI token, note the letter swap) is accepted with a WARNING and redirected to --spec odps-4.1. Update any scripts that use the old token.
Notes
- Despite the source file being named
odps_standard.py, the canonical command name registered influid --helpisodps-bitol. This avoids confusion with the LF/ODPI variant. fluid generate standard --format odps-bitolis an alias of--format odps: both emit the same Bitol v1.0.0 document. Only the default output filename differs. It is not a stricter mode.- For the unified dispatch (Bitol + LF/ODPI), use
fluid odps. - For the Open Data Contract Standard (ODCS), use
fluid odcs. - Validation keys on the document's own
apiVersion(v1.0.0orv1.1.0; since v0.13.1), requireskind: DataProduct, and verifies output ports have anamefield. Custom orgtypevalues round-trip verbatim.