AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

basin

Build and troubleshoot Cloudflare Basin analytics workflows with Basin Pipelines, Basin Catalog, and Basin SQL. Use for streaming data into R2 Iceberg tables, managing catalogs, or querying those tables; also use for requests using the former Data Platform, Pipelines, R2 Data Catalog, or R2 SQL names.

Original source
cloudflare
License
Apache-2.0
Pinned revision
e44f580f9c4fa3bf268e284ae7706c7954ba31fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read cloudflare--basin at revision e44f580f9c4fa3bf268e284ae7706c7954ba31fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 17

references/catalog/patterns.md

Basin Catalog Patterns

Choose the engine based on the project's existing runtime and workload, then retrieve its current connection example.

| Need | Starting point | |------|----------------| | Python catalog operations and ingestion without a Spark deployment | PyIceberg | | Existing Spark ETL and distributed table processing | PySpark | | Connect an existing SQL engine | Engine configuration guides | | Query through Cloudflare's serverless SQL service | Basin SQL | | Stream events into tables | Basin Pipelines patterns |

Use the discovered Catalog URI and Warehouse name from configuration. Match dependencies to the installed engine and the current guide instead of adopting a universal pinned Spark/Iceberg combination.

Plan ingestion, query, and maintenance responsibilities together. Prefer automatic table maintenance when it meets the workload; align retention with time-travel needs before enabling expiration. For engine-specific partitioning, schema evolution, or manual procedures, consult that engine's linked upstream documentation and verify behavior on representative data.

When multiple writers share a table, design recovery around the actual failed operation and the engine's commit semantics. Reproduce conflicts and ensure retries do not duplicate application work. See API selection and troubleshooting.