File size: 3,734 Bytes
e8c001c
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
---
id: offline-compute_MySQL_mysql_008
name: 消费组治理项明细提取
category: offline-compute/MySQL
timeout_seconds: 1800
modality: pure-text
engine: mysql
---
## Prompt
任务目标:从消费特征增量表提取近90天有消费量且非 reader 类型的消费组治理项明细。

**输入表**`internal_platform_db.dws_mq_consumption_feature_d_increase_mysql_008`(消费特征增量表)

(表结构与字段含义请自行连接数据库查询确认)

**处理规则**1. 过滤条件:`dt = '20260507'` AND `(total_consume_last_90d <> 0 AND total_consume_last_90d IS NOT NULL)` AND `is_reader = 0`
2. 派生字段:
   - `mq_full_topic`:若 `tenant``namespaces` 均非 NULL,拼接 `'persistent://' + tenant + '/' + namespaces + '/' + topic`;否则取 `topic`
   - `app_group`:取自 `dw_appgroup`
   - `consumergroup_incharge``COALESCE(consumergroup_incharge, bid_incharge)`,即消费组负责人为空时取 bid 负责人
   - `consumergroup_description`:取自 `usage_desc`
   - `hitted_gov_items`:固定 NULL
   - `governance_benefit_estimate`:固定 NULL
3. 无 Join,单表处理

**输出要求**- 目标表:`internal_platform_db.ads_mq_consumergroup_governance_item_d_cand_mysql_008`
- 输出字段顺序为:`dt``business_id``business_name``cluster_set``mq_full_topic``topic``consumergroup``system_belong``bg``category_name``app_group``consumergroup_incharge``last_operator``consumergroup_description``create_time``modify_time``bid_incharge``cluster_id``has_metadata``total_produce_pkg_d``total_consume_pkg_d``consume_ratio``total_produce_pkg_last_7d``total_produce_pkg_last_30d``total_produce_pkg_last_90d``total_consume_last_7d``consume_ratio_last_7d``backlog_ratio_last_7d``total_consume_last_30d``consume_ratio_last_30d``backlog_ratio_last_30d``total_consume_last_90d``consume_ratio_last_90d``backlog_ratio_last_90d``backlog_days_last_30d``hitted_gov_items``governance_benefit_estimate`
- 字段类型:
  - `dt` VARCHAR(8)
  - `mq_full_topic` VARCHAR(512)
  - `app_group` VARCHAR(256)
  - `consumergroup_incharge` VARCHAR(256)
  - `consumergroup_description` VARCHAR(256)
  - `has_metadata` TINYINT
  - `total_produce_pkg_d` BIGINT
  - `total_consume_pkg_d` BIGINT
  - `consume_ratio` VARCHAR(256)
  - `total_produce_pkg_last_7d` BIGINT
  - `total_produce_pkg_last_30d` BIGINT
  - `total_produce_pkg_last_90d` BIGINT
  - `total_consume_last_7d` BIGINT
  - `consume_ratio_last_7d` VARCHAR(256)
  - `backlog_ratio_last_7d` VARCHAR(256)
  - `total_consume_last_30d` BIGINT
  - `consume_ratio_last_30d` VARCHAR(256)
  - `backlog_ratio_last_30d` VARCHAR(256)
  - `total_consume_last_90d` BIGINT
  - `consume_ratio_last_90d` VARCHAR(256)
  - `backlog_ratio_last_90d` VARCHAR(256)
  - `backlog_days_last_30d` INT
  - `hitted_gov_items` VARCHAR(256)
  - `governance_benefit_estimate` DOUBLE
  - 其余字符串字段均为 VARCHAR(256)
- 写入方式:使用 `INSERT INTO ... SELECT ...` 写入目标表
- 如果目标表不存在,请先按 MySQL InnoDB 标准建表,再写入数据
- 请使用标准 MySQL 语法,不要使用 Hive/Spark SQL 方言

**环境与执行说明**- 你的最终产出必须写入文件 `/tmp_workspace/result.py`,不能写 result.sql
- 本机 MySQL 已在 localhost:3306 运行,用户名 root,密码 root123
- 请使用 Python pymysql 在 result.py 中执行 SQL(不要用 mysql 命令行)
- 脚本需要包含完整的建表(如目标表不存在)+ 写入数据的逻辑
- 写出 result.py 后,你必须自己执行 `python3 /tmp_workspace/result.py` 验证它能成功运行并产出正确数据