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/gotchas.md

Basin Catalog Troubleshooting

Identify whether the failure occurs in catalog administration, engine metadata access, or underlying object access before changing permissions or client settings.

| Check | Documentation | |-------|---------------| | Catalog enablement, Catalog URI, or Warehouse mismatch | Manage catalogs | | Reader/writer token scope or file-access denial | Engine authentication — inspect both catalog and storage permissions | | Missing maintenance credentials or wrong table/catalog configuration | Control-plane API and enable compaction | | Compaction backlog, retention, or orphaned files | Table maintenance | | PyIceberg connection or table creation | PyIceberg configuration | | Spark dependency, credential-vending, or signing configuration | PySpark configuration | | Deleted data is still present | Deleting data | | Catalog request or maintenance-job diagnosis | Metrics and analytics |

Compare the client's configured URI and warehouse with the actual catalog values. Test a read operation first; do not grant write access merely to resolve a reader's failure. For schema or concurrency errors, inspect the installed engine's behavior and current table metadata before retrying. The get-table note is not a substitute for verifying the service's response contract.

See configuration and patterns for implementation choices.