Skip to content

feat(providers-static): add static provider crate with config#1948

Merged
LNSD merged 1 commit intomainfrom
lnsd/feat-providers-static-crate
Mar 10, 2026
Merged

feat(providers-static): add static provider crate with config#1948
LNSD merged 1 commit intomainfrom
lnsd/feat-providers-static-crate

Conversation

@LNSD
Copy link
Contributor

@LNSD LNSD commented Mar 10, 2026

Introduce a new provider type for serving static datasets from object stores, following the same crate structure as existing providers (evm-rpc, firehose, solana).

  • Add StaticProviderConfig with object store root, cache size, and schema inference settings
  • Add StaticProviderKind zero-sized type with serde, schema, and string comparison impls
  • Add gen sub-crate for JSON schema generation via gen_schema_provider cfg flag
  • Update provider feature docs: rename from provider-extractor-* to provider-*, add status frontmatter
  • Register crate in workspace, monitoring logging filter, and justfile codegen tasks

…ema generation

Introduce a new provider type for serving pre-computed CSV datasets from object stores,
following the same crate structure as existing providers (evm-rpc, firehose, solana).

- Add `StaticProviderConfig` with object store root, cache size, and schema inference settings
- Add `StaticProviderKind` zero-sized type with serde, schema, and string comparison impls
- Add `gen` sub-crate for JSON schema generation via `gen_schema_provider` cfg flag
- Update provider feature docs: rename from `provider-extractor-*` to `provider-*`, add status frontmatter
- Register crate in workspace, monitoring logging filter, and justfile codegen tasks

Signed-off-by: Lorenzo Delgado <lorenzo@edgeandnode.com>
@LNSD LNSD requested review from Theodus and mitchhs12 March 10, 2026 18:08
@LNSD LNSD self-assigned this Mar 10, 2026
@LNSD LNSD requested a review from leoyvens March 10, 2026 18:08
Copy link
Member

@Theodus Theodus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Depending on how we expect this to evolve, we may want to name the dataset kind static-csv. But it can remain as just static if we expect that this provider might eventually support other formats.

@LNSD
Copy link
Contributor Author

LNSD commented Mar 10, 2026

LGTM. Depending on how we expect this to evolve, we may want to name the dataset kind static-csv. But it can remain as just static if we expect that this provider might eventually support other formats.

The kind here refers to the "provider kind", and I think we can have a many "dataset kinds" to one "provider kind" relationship. Depending on how we define the dataset manifest details, we can have static-csv, static-json, and static-parquet dataset kinds and serve them via the static provider.

@LNSD LNSD merged commit 90b6f00 into main Mar 10, 2026
15 of 16 checks passed
@LNSD LNSD deleted the lnsd/feat-providers-static-crate branch March 10, 2026 19:01
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