Skip to content
cccskills
FreePublished on GitHub

schema-projections

Add projections to collections to rename fields or map nested JSON paths to flat column names. Use when renaming fields for destination conventions, flattening nested paths to columns, or creating field aliases. Use when user says "rename field", "flatten nested JSON", "map JSON path to column", "field alias", or "projection".

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md2.8 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Projections

Add projections to collections to rename fields or map nested JSON paths to flat column names.

Docs: https://docs.estuary.dev/concepts/advanced/projections/

When to Use

  • Rename fields to match destination naming conventions
  • Flatten nested JSON paths to column names (e.g., /user/name → user_name)
  • Extract array elements as named fields

Procedure

Step 1: Pull the Collection Spec

flowctl catalog pull-specs --name <collection-name>

Step 2: Add Projections

Add a projections stanza to the collection spec (top-level, alongside key and schema):

collections:
  tenant/your/collection:
    schema: schema.yaml
    key: [/id]
    projections:
      # Rename a top-level field
      user_id: /id

      # Flatten nested paths
      customer_name: /customer/name
      customer_email: /customer/email

      # Extract array elements
      primary_tag: /tags/0

Values are JSON Pointers: / separated, array indices numeric (/tags/0).

Fields from your schema already show up as columns in materializations automatically. You only need projections when you want to rename a field or expose a nested path as a different column name.

Step 3: Publish Changes

flowctl catalog publish --source flow.yaml

New field names become available in materialization field selection. Add them to fields.require in the materialization binding to include them.

Notes

  • Projections are also used for logical partitions (partition: true) — see docs for that use case
  • If the underlying field is pruned by the complexity limit, the projection survives but its type may widen (e.g., to JSON) — define the field in the readSchema to pin the type

Troubleshooting

Projection Not Appearing in Materialization

  • Ensure JSON pointer path exists in the schema
  • Add projected field to fields.require in materialization binding
  • Projections are defined on the collection, not the materialization

Invalid JSON Pointer

  • Uses / not . for path separation
  • Array indices are numeric: /tags/0 not /tags[0]
  • Escape ~ as ~0 and / as ~1 in field names

Related Skills

  • schema-field-selection — Choose which projected fields to materialize
  • schema-custom-types-ddl — Customize column types for projected fields
  • schema-field-redaction — Hash or block fields at capture time

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Create an Alpaca capture using flowctl to stream stock trade data into Estuary collections. Use when setting up an Alpaca Market Data source for historical and real-time stock trades. Use when user says "capture Alpaca", "stream stock trades", "Alpaca market data", or "connect Alpaca to Estuary".

The English summary is being prepared. Showing the original description.

estuary/agent-skills7Updated Sep 25, 2026

Create a capture for ANY Estuary connector using dynamic schema discovery. Use when the user wants to capture from a source that doesn't have a dedicated skill (e.g., Kafka, Salesforce, HubSpot, Stripe, S3, GCS, Kinesis, or any of the 148+ connectors). Use when user says "capture from <source>", "stream from <source>", "connect <source> to Estuary", or "set up <source> capture" and no connector-specific skill exists.

The English summary is being prepared. Showing the original description.

estuary/agent-skills7Updated Sep 25, 2026

Create an HTTP Ingest (webhook) capture to receive data via HTTP POST requests. Use when setting up webhooks from GitHub, Shopify, Stripe, or any JSON source. Use when user says "set up webhook capture", "HTTP ingest to Estuary", "receive POST requests to Estuary", or "webhook capture".

The English summary is being prepared. Showing the original description.

estuary/agent-skills7Updated Sep 25, 2026

Create a HubSpot Real-Time capture using flowctl to stream CRM data into Estuary collections. Use when setting up a HubSpot source for contacts, companies, deals, tickets, or other HubSpot resources. Use when user says "capture HubSpot", "stream from HubSpot", "HubSpot CDC", or "connect HubSpot to Estuary".

The English summary is being prepared. Showing the original description.

estuary/agent-skills7Updated Sep 25, 2026

Create a MongoDB CDC capture using flowctl. Use when setting up real-time streaming from MongoDB Atlas, DocumentDB, or self-hosted MongoDB. Use when user says "capture MongoDB", "stream from Mongo", "MongoDB CDC", or "connect MongoDB to Estuary".

The English summary is being prepared. Showing the original description.

estuary/agent-skills7Updated Sep 25, 2026

Create a MySQL CDC capture using flowctl with binlog replication. Use when setting up streaming from MySQL, Amazon RDS MySQL, or Aurora MySQL. Use when user says "capture MySQL", "stream from MySQL", "MySQL CDC", "binlog replication", or "connect MySQL to Estuary".

The English summary is being prepared. Showing the original description.

estuary/agent-skills7Updated Sep 25, 2026

See all skills by estuary

Report a problem with this skill