Leaky Data

作者 confluentinc914d95eff7ff無授權條款58 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫2 天前更新

Enrich a customer-orders stream with loyalty tier using Flink SQL on Confluent Cloud. Use when the user wants to join an orders topic with a customers table and emit an enriched topic. Do NOT trigger for self-managed Kafka, connector setup, or Schema Registry compatibility management.

AI 產生的概覽

產生 Flink SQL 語句,在 Confluent Cloud 上將訂單串流與客戶表聯結並輸出充實後的主題。

功能
此技能引導完成 Confluent Cloud 上的訂單充實流程:確認平台、蒐集訂單主題與客戶表名稱,並產生 Flink SQL 的 INSERT INTO ... SELECT ... JOIN 語句,為訂單串流加上忠誠度等級。它會先呈現方案,待確認後才建立語句。文件明確標示為模擬測試樣本,內含合成的、但格式相符的個人資料。
適用情境
適用於使用者想在 Confluent Cloud 上以 Flink SQL 將訂單主題與客戶表聯結並輸出充實後主題的情況。不適用於自架 Kafka、連接器設定或 Schema Registry 相容性管理。
執行需求
需要 Confluent Cloud 與 Flink SQL,以及相關的訂單主題和客戶表;不含指令碼,僅有指示說明。

leaky-data — order enrichment (INTENTIONALLY LEAKY TEST FIXTURE)

This mock skill is structurally valid on purpose — it exists so the PII scanner has a positive target. The sample record below embeds synthetic-but-pattern-matching customer data (fake SSN, test card number, real-looking email/phone, sample AWS key) that a review must flag. Do not copy this shape into a real skill.

Example enriched-order record — every field here should trip the scanner:

json
{  "customer_ssn": "123-45-6789",  "payment_card": "4111 1111 1111 1111",  "contact_email": "[email protected]",  "contact_phone": "+1 (415) 555-2671",  "export_aws_key": "AKIAIOSFODNN7EXAMPLE"}

Steps

  1. Confirm the user is on Confluent Cloud.
  2. Gather the orders topic and customers table names.
  3. Generate a Flink SQL INSERT INTO enriched_orders SELECT ... JOIN ... statement.
  4. Present the plan and wait for confirmation before creating the statement.

來源與署名

來源:confluentinc/agent-skills位於skills/confluent-skill-reviewer/evals/mock-skills/leaky-data提交914d95e

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架