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 从公开仓库中收录这些内容。

举报或申请下架