# Generated by API Evangelist (build-phrasing.py). Our phrasing, not observed demand.
overlay: 1.0.0
info:
  title: API Evangelist conversational phrasing for Confluent Cloud Materialized Tables (sql/v1) API
  version: 1.0.0
extends: openapi/confluent-materialized-tables-sql-v1-api-openapi.yml
actions:
- target: $.info
  update:
    x-apievangelist-phrasing:
      method: generated
      generated: '2026-09-26'
      generator: build-phrasing.py
      label: Generated by API Evangelist
      operations: 5
- target: $.paths['/sql/v1/organizations/{organization_id}/environments/{environment_id}/materialized-tables'].get
  update:
    x-apievangelist-phrasing:
      intent: List materialized tables in an environment
      effect: read
      questions:
      - Which Flink materialized tables exist in my environment?
      - Can I page through all materialized tables?
      instructions:
      - text: List materialized tables in environment {environment_id}, org {organization_id}.
        slots:
          environment_id: path.environment_id
          organization_id: path.organization_id
      - text: Show all materialized tables in env {environment_id} of org {organization_id}, {page_size} per page.
        slots:
          environment_id: path.environment_id
          organization_id: path.organization_id
          page_size: query.page_size
      method: generated
      generated: '2026-09-26'
- target: $.paths['/sql/v1/organizations/{organization_id}/environments/{environment_id}/databases/{kafka_cluster_id}/materialized-tables'].post
  update:
    x-apievangelist-phrasing:
      intent: Create a materialized table
      effect: write
      questions:
      - How do I create a continuously maintained materialized table with Flink SQL in Confluent?
      - What query and options go into a materialized table spec?
      instructions:
      - text: Create materialized table {name} in database {kafka_cluster_id}, env {environment_id}, org {organization_id} with spec {spec}.
        slots:
          name: requestBody.name
          kafka_cluster_id: path.kafka_cluster_id
          environment_id: path.environment_id
          organization_id: path.organization_id
          spec: requestBody.spec
      - text: Define a new materialized table called {name} on cluster {kafka_cluster_id} (env {environment_id}, org {organization_id}).
        slots:
          name: requestBody.name
          kafka_cluster_id: path.kafka_cluster_id
          environment_id: path.environment_id
          organization_id: path.organization_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/sql/v1/organizations/{organization_id}/environments/{environment_id}/databases/{kafka_cluster_id}/materialized-tables/{table_name}'].get
  update:
    x-apievangelist-phrasing:
      intent: Get a materialized table
      effect: read
      questions:
      - What query and status does one materialized table have?
      - Can I read a materialized table's definition by name?
      instructions:
      - text: Get materialized table {table_name} in database {kafka_cluster_id}, env {environment_id}, org {organization_id}.
        slots:
          table_name: path.table_name
          kafka_cluster_id: path.kafka_cluster_id
          environment_id: path.environment_id
          organization_id: path.organization_id
      - text: Show the status of materialized table {table_name} on cluster {kafka_cluster_id} (env {environment_id}, org {organization_id}).
        slots:
          table_name: path.table_name
          kafka_cluster_id: path.kafka_cluster_id
          environment_id: path.environment_id
          organization_id: path.organization_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/sql/v1/organizations/{organization_id}/environments/{environment_id}/databases/{kafka_cluster_id}/materialized-tables/{table_name}'].put
  update:
    x-apievangelist-phrasing:
      intent: Update or evolve a materialized table
      effect: write
      questions:
      - Can I change a materialized table's query, compute pool or columns?
      - Is it possible to stop a materialized table without deleting it?
      instructions:
      - text: Evolve materialized table {table_name} in database {kafka_cluster_id}, env {environment_id}, org {organization_id} to spec {spec}.
        slots:
          table_name: path.table_name
          kafka_cluster_id: path.kafka_cluster_id
          environment_id: path.environment_id
          organization_id: path.organization_id
          spec: requestBody.spec
      - text: Stop materialized table {table_name} on cluster {kafka_cluster_id} in env {environment_id}, org {organization_id} by updating it.
        slots:
          table_name: path.table_name
          kafka_cluster_id: path.kafka_cluster_id
          environment_id: path.environment_id
          organization_id: path.organization_id
      method: generated
      generated: '2026-09-26'
- target: $.paths['/sql/v1/organizations/{organization_id}/environments/{environment_id}/databases/{kafka_cluster_id}/materialized-tables/{table_name}'].delete
  update:
    x-apievangelist-phrasing:
      intent: Delete a materialized table
      effect: destructive
      questions:
      - How do I drop a materialized table I no longer need?
      - Can I delete a materialized table by name?
      instructions:
      - text: Delete materialized table {table_name} from database {kafka_cluster_id}, env {environment_id}, org {organization_id}.
        slots:
          table_name: path.table_name
          kafka_cluster_id: path.kafka_cluster_id
          environment_id: path.environment_id
          organization_id: path.organization_id
      - text: Drop the materialized table {table_name} on cluster {kafka_cluster_id} in env {environment_id}, org {organization_id}.
        slots:
          table_name: path.table_name
          kafka_cluster_id: path.kafka_cluster_id
          environment_id: path.environment_id
          organization_id: path.organization_id
      method: generated
      generated: '2026-09-26'