Skip to content

docs(loader): correct directive, header and operations docs - #333

Merged
catinspace-au merged 1 commit into
mainfrom
docs/factcheck-c
Nov 12, 2026
Merged

catinspace-au merged 1 commit into
mainfrom
docs/factcheck-c

Conversation

@catinspace-au

Copy link
Copy Markdown
Contributor

The @computed page replaces a function catalogue the loader does not have with scalo's restricted profile rules. Each value is one CEL expression.

  • A @computed expression that fails per record leaves the column empty with no error. One that does not compile is logged and skipped.
  • GeoIP, reputation and risk come from the geoip and enrichment config, not from @computed.
  • The Python REST API spec, the chaining and cost sections, the UI builder flow and the version history are gone. No such routes or package exist.
  • The Rust example uses only the TableTags calls that exist.
  • The loader creates no table. Auto-init, engine detection, custom profiles and the v1 migration are gone from the common header page.
  • _org_id comes from routing.org_id_field alone, never a column directive.
  • Config examples are YAML with default_db dfe and default_table main.
  • Operations lists the DFE_LOADER_* env names, the clickhouse.protocol guard and scaling_circuit_open. The added scaling section gives the DFE default: CPU 70% plus the pressure trigger, cleared on slim.
  • The transports are Kafka and gRPC. IPv4 is little-endian on the wire. routing.source_to_table has a settings row.
  • Dropped contributor notes from types.md, tls.md and operations.md.

The @computed page now documents scalo's restricted profile rules. The loader has no function catalogue. Each value is one CEL expression.

- A @computed expression that fails per record leaves the column empty with no error. One that does not compile is logged and skipped.
- GeoIP, reputation and risk come from the geoip and enrichment config. @computed provides none of them.
- @source and @renamed resolve to the same source-path list. The page no longer describes one as a copy and the other as a move.
- The Python REST API spec, the chaining and cost sections, the UI builder flow and the version history are gone. No such routes or package exist.
- The Rust example uses only the TableTags calls that exist.
- The loader creates no table. Auto-init, engine detection, custom profiles and the v1 migration are gone from the common header page.
- _org_id comes from routing.org_id_field alone, never a column directive.
- Config examples are YAML with default_db dfe and default_table main.
- Operations lists the DFE_LOADER_* env names, the clickhouse.protocol guard and scaling_circuit_open. The scaling section gives the DFE default: CPU 70% plus the pressure trigger. The slim profile drops the pressure trigger.
- The transports are Kafka and gRPC. IPv4 is little-endian on the wire. routing.source_to_table has a settings row.
- Dropped contributor notes from types.md, tls.md and operations.md.
@catinspace-au
catinspace-au merged commit 7e2fd45 into main Nov 12, 2026
14 checks passed
@catinspace-au
catinspace-au deleted the docs/factcheck-c branch November 12, 2026 06:41
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.

1 participant