@clickzetta/cz-cli-darwin-x64 0.3.87 → 0.3.88
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/bin/cz-cli +0 -0
- package/bin/skills/clickzetta-dynamic-table/SKILL.md +169 -169
- package/bin/skills/clickzetta-dynamic-table/best-practices/dimension-table-join-guide.md +126 -126
- package/bin/skills/clickzetta-dynamic-table/best-practices/medallion-and-stream-patterns.md +25 -25
- package/bin/skills/clickzetta-dynamic-table/best-practices/non-partitioned-merge-into-warning.md +48 -48
- package/bin/skills/clickzetta-dynamic-table/best-practices/performance-optimization.md +51 -51
- package/bin/skills/clickzetta-dynamic-table/best-practices/scheduling-guide.md +59 -59
- package/bin/skills/clickzetta-dynamic-table/dt-creator/SKILL.md +8 -7
- package/bin/skills/clickzetta-dynamic-table/dt-creator/references/dt-declaration-strategy.md +99 -99
- package/bin/skills/clickzetta-dynamic-table/dt-creator/references/incremental-config-reference.md +188 -188
- package/bin/skills/clickzetta-dynamic-table/dt-creator/references/refresh-history-guide.md +117 -117
- package/bin/skills/clickzetta-dynamic-table/dt-creator/references/sql-limitations.md +29 -29
- package/bin/skills/clickzetta-dynamic-table/dynamic-table-alter/SKILL.md +80 -79
- package/bin/skills/clickzetta-dynamic-table/sql-to-dt/SKILL.md +15 -15
- package/bin/skills/clickzetta-dynamic-table/sql-to-dt/references/sql2dt-column-validation-rules.md +61 -61
- package/bin/skills/clickzetta-dynamic-table/sql-to-dt/references/sql2dt-conversion-rules.md +100 -100
- package/bin/skills/clickzetta-dynamic-table/sql-to-dt/references/sql2dt-placeholder-rules.md +64 -64
- package/bin/skills/clickzetta-dynamic-table/sql-to-dt/references/sql2dt-refresh-rules.md +32 -32
- package/bin/skills/clickzetta-dynamic-table/sql-to-dt/references/sql2dt-self-reference-rules.md +21 -21
- package/bin/skills/clickzetta-dynamic-table/sql-to-dt/references/sql2dt-workflow.md +71 -71
- package/bin/skills/clickzetta-sql-pipeline-manager/SKILL.md +203 -202
- package/bin/skills/clickzetta-sql-pipeline-manager/references/dynamic-table.md +62 -62
- package/bin/skills/clickzetta-sql-pipeline-manager/references/materialized-view.md +34 -34
- package/bin/skills/clickzetta-sql-pipeline-manager/references/pipe.md +61 -61
- package/bin/skills/clickzetta-sql-pipeline-manager/references/table-stream.md +41 -41
- package/bin/skills/clickzetta-table-stream-pipeline/SKILL.md +103 -101
- package/package.json +1 -1
package/bin/cz-cli
CHANGED
|
Binary file
|
|
@@ -1,230 +1,230 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: clickzetta-dynamic-table
|
|
3
3
|
description: |
|
|
4
|
-
ClickZetta Dynamic Table
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
-
|
|
8
|
-
-
|
|
9
|
-
-
|
|
10
|
-
- SQL
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
"
|
|
14
|
-
"
|
|
15
|
-
"
|
|
16
|
-
"
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
SQL
|
|
4
|
+
ClickZetta Dynamic Table usage guide and routing hub.
|
|
5
|
+
|
|
6
|
+
[Trigger scenarios]
|
|
7
|
+
- General consultation: Dynamic Table introduction, usage, best practices, performance optimization, incremental configuration
|
|
8
|
+
- Creation guidance: DT declaration strategy, SQL support matrix, refresh history queries
|
|
9
|
+
- Modification operations: detected and automatically delegated to the dynamic-table-alter sub-skill
|
|
10
|
+
- SQL conversion: detected and automatically delegated to the sql-to-dt sub-skill
|
|
11
|
+
|
|
12
|
+
[Trigger keywords]
|
|
13
|
+
"how to use dynamic table", "DT introduction", "dynamic table best practices", "dynamic table performance optimization",
|
|
14
|
+
"incremental computation configuration", "dimension table JOIN", "dynamic table refresh history", "static partition DT",
|
|
15
|
+
"dynamic partition DT", "state table management", "non-partitioned table risks", "create dynamic table",
|
|
16
|
+
"dynamic table scheduling", "REFRESH INTERVAL", "dynamic table alerts"
|
|
17
|
+
|
|
18
|
+
[Non-trigger scenarios]
|
|
19
|
+
Modification operations ("modify dynamic table", "add column", "change interval", etc.) → use dynamic-table-alter
|
|
20
|
+
SQL conversion ("convert to DT", "INSERT OVERWRITE to DT", etc.) → use sql-to-dt
|
|
21
21
|
---
|
|
22
22
|
|
|
23
|
-
# Dynamic Table
|
|
23
|
+
# Dynamic Table Usage Guide — Routing & Index
|
|
24
24
|
|
|
25
|
-
|
|
25
|
+
This skill is the **knowledge hub and router** for ClickZetta Dynamic Tables. It provides reference documentation based on user intent, or automatically delegates to specialized operation sub-skills.
|
|
26
26
|
|
|
27
27
|
---
|
|
28
28
|
|
|
29
|
-
##
|
|
29
|
+
## Use Case Categories
|
|
30
30
|
|
|
31
|
-
### 1.
|
|
31
|
+
### 1. General Consultation & Learning (handled by this skill)
|
|
32
32
|
|
|
33
|
-
|
|
34
|
-
-
|
|
35
|
-
-
|
|
36
|
-
-
|
|
33
|
+
**Applicable scenarios:**
|
|
34
|
+
- Looking up best practices and performance optimization recommendations
|
|
35
|
+
- Finding documentation for specific configuration options
|
|
36
|
+
- Learning how to create Dynamic Tables
|
|
37
37
|
|
|
38
|
-
|
|
39
|
-
- "
|
|
40
|
-
- "
|
|
41
|
-
- "
|
|
42
|
-
- "
|
|
43
|
-
- "
|
|
44
|
-
- "
|
|
45
|
-
- "
|
|
46
|
-
- "
|
|
38
|
+
**Trigger keywords:**
|
|
39
|
+
- "how to use dynamic table", "DT introduction", "what is Dynamic Table"
|
|
40
|
+
- "dynamic table best practices", "DT performance optimization", "dynamic table performance tuning"
|
|
41
|
+
- "incremental computation configuration", "refresh strategy", "state table management"
|
|
42
|
+
- "how to configure dimension table JOIN", "non-partitioned table risks"
|
|
43
|
+
- "how to query dynamic table refresh history", "REFRESH HISTORY"
|
|
44
|
+
- "static partition DT", "dynamic partition DT", "DT declaration strategy"
|
|
45
|
+
- "what SQL does dynamic table support", "dynamic table SQL limitations"
|
|
46
|
+
- "create dynamic table", "new dynamic table", "CREATE DYNAMIC TABLE"
|
|
47
47
|
|
|
48
|
-
|
|
48
|
+
**Handling:** Provide content and guidance from the relevant reference documents.
|
|
49
49
|
|
|
50
50
|
---
|
|
51
51
|
|
|
52
|
-
### 2.
|
|
52
|
+
### 2. Modify an Existing Dynamic Table (automatically delegated to dynamic-table-alter sub-skill)
|
|
53
53
|
|
|
54
|
-
|
|
55
|
-
-
|
|
56
|
-
-
|
|
57
|
-
-
|
|
54
|
+
**Applicable scenarios:**
|
|
55
|
+
- Modifying the structure or properties of an existing Dynamic Table
|
|
56
|
+
- Suspending/resuming Dynamic Table refresh
|
|
57
|
+
- Adding/dropping columns, changing refresh interval, modifying query definition
|
|
58
58
|
|
|
59
|
-
|
|
60
|
-
- "
|
|
61
|
-
- "
|
|
62
|
-
- "
|
|
63
|
-
- "
|
|
64
|
-
- "ALTER DYNAMIC TABLE"
|
|
65
|
-
- "
|
|
59
|
+
**Trigger keywords:**
|
|
60
|
+
- "modify dynamic table", "add column to dynamic table", "drop column from dynamic table"
|
|
61
|
+
- "change refresh interval", "modify REFRESH_INTERVAL"
|
|
62
|
+
- "suspend dynamic table", "resume dynamic table", "SUSPEND", "RESUME"
|
|
63
|
+
- "rename column", "modify column comment", "modify table comment"
|
|
64
|
+
- "ALTER DYNAMIC TABLE", "CREATE OR REPLACE DYNAMIC TABLE"
|
|
65
|
+
- "modify DT query definition", "modify AS SELECT"
|
|
66
66
|
|
|
67
|
-
|
|
68
|
-
> ⚠️
|
|
69
|
-
>
|
|
70
|
-
> - 5
|
|
71
|
-
> - 5
|
|
67
|
+
**Handling:**
|
|
68
|
+
> ⚠️ Modification intent detected — immediately load the dynamic-table-alter sub-skill.
|
|
69
|
+
> That sub-skill provides a complete workflow for 10 types of modification operations:
|
|
70
|
+
> - 5 direct ALTER operations: suspend, resume, set_comment, rename_column, set_column_comment
|
|
71
|
+
> - 5 CREATE OR REPLACE operations: add_column, drop_column, alter_column, set_refresh_interval, set_select
|
|
72
72
|
|
|
73
73
|
---
|
|
74
74
|
|
|
75
|
-
### 3. SQL
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
-
|
|
79
|
-
-
|
|
80
|
-
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
- "
|
|
84
|
-
- "INSERT OVERWRITE
|
|
85
|
-
- "Hive SQL
|
|
86
|
-
- "
|
|
87
|
-
- "
|
|
88
|
-
|
|
89
|
-
|
|
90
|
-
> ⚠️
|
|
91
|
-
>
|
|
92
|
-
> "
|
|
93
|
-
>
|
|
94
|
-
> 1.
|
|
95
|
-
> 2.
|
|
96
|
-
> 3.
|
|
97
|
-
> 4.
|
|
98
|
-
> 5.
|
|
99
|
-
> 6.
|
|
75
|
+
### 3. Convert SQL to Dynamic Table (automatically delegated to sql-to-dt sub-skill)
|
|
76
|
+
|
|
77
|
+
**Applicable scenarios:**
|
|
78
|
+
- Converting CREATE TABLE + INSERT OVERWRITE from Hive/Spark or any batch processing system to DT
|
|
79
|
+
- Bulk migration of traditional ETL to Dynamic Tables
|
|
80
|
+
- Auto-generating companion files for refresh, backfill, etc.
|
|
81
|
+
|
|
82
|
+
**Trigger keywords:**
|
|
83
|
+
- "convert to DT", "sql to dt", "convert to dynamic table"
|
|
84
|
+
- "INSERT OVERWRITE to DT", "DDL conversion"
|
|
85
|
+
- "Hive SQL to ClickZetta", "Spark SQL to dynamic table"
|
|
86
|
+
- "bulk convert ETL", "migrate to dynamic table"
|
|
87
|
+
- "create dynamic table", "new dynamic table", "CREATE DYNAMIC TABLE"
|
|
88
|
+
|
|
89
|
+
**Handling:**
|
|
90
|
+
> ⚠️ SQL conversion intent detected — immediately load the sql-to-dt sub-skill.
|
|
91
|
+
> If the user says "create dynamic table" but has not provided a DDL and INSERT OVERWRITE, proactively prompt:
|
|
92
|
+
> "Please provide the original CREATE TABLE DDL and INSERT OVERWRITE statement, and I can automatically generate the corresponding Dynamic Table DDL along with companion refresh and backfill files."
|
|
93
|
+
> That sub-skill provides a 6-step automatic conversion workflow:
|
|
94
|
+
> 1. Pre-process input (remove ALTER, ANALYZE, comments)
|
|
95
|
+
> 2. Placeholder replacement (convert to SESSION_CONFIGS)
|
|
96
|
+
> 3. Self-reference detection
|
|
97
|
+
> 4. Core conversion (merge DDL + INSERT into CREATE OR REPLACE)
|
|
98
|
+
> 5. Column validation
|
|
99
|
+
> 6. Generate companion files (refresh, prev_refresh, backfill)
|
|
100
100
|
|
|
101
101
|
---
|
|
102
102
|
|
|
103
|
-
##
|
|
103
|
+
## Knowledge Base Directory
|
|
104
104
|
|
|
105
|
-
### dt-creator/ —
|
|
105
|
+
### dt-creator/ — Dynamic Table Creation Reference
|
|
106
106
|
|
|
107
|
-
|
|
108
|
-
- **dt-declaration-strategy.md** —
|
|
109
|
-
-
|
|
110
|
-
-
|
|
111
|
-
-
|
|
107
|
+
**Contents:**
|
|
108
|
+
- **dt-declaration-strategy.md** — Declaration strategy and selection between static partition DT and dynamic partition DT
|
|
109
|
+
- Static partition DT: uses SESSION_CONFIGS() to pass partition parameters; each partition refreshes independently
|
|
110
|
+
- Dynamic partition DT: no partition parameters; processes all incremental data in one pass
|
|
111
|
+
- Decision tree: choose the appropriate partition strategy based on data patterns
|
|
112
112
|
|
|
113
|
-
- **sql-limitations.md** —
|
|
113
|
+
- **sql-limitations.md** — SQL patterns supported by incremental computation (support status for JOIN, aggregation, window functions, etc., and limitations such as VIEW/external tables not supporting incremental)
|
|
114
114
|
|
|
115
|
-
- **incremental-config-reference.md** —
|
|
116
|
-
-
|
|
117
|
-
-
|
|
118
|
-
-
|
|
119
|
-
-
|
|
120
|
-
- DT
|
|
121
|
-
- Backfill
|
|
122
|
-
-
|
|
115
|
+
- **incremental-config-reference.md** — Complete reference for incremental refresh configuration options
|
|
116
|
+
- Refresh strategy: force full refresh, try incremental with fallback
|
|
117
|
+
- Source table characteristic declarations: dimension tables, append-only tables
|
|
118
|
+
- Full refresh fallback triggers: based on table changes or change volume
|
|
119
|
+
- State table management: enable/disable, lifecycle, rebuild, schema specification
|
|
120
|
+
- DT definition changes: compatibility check for CREATE OR REPLACE
|
|
121
|
+
- Backfill: historical partition data correction
|
|
122
|
+
- Partitioned table write behavior: overwrite vs append mode
|
|
123
123
|
|
|
124
|
-
- **refresh-history-guide.md** —
|
|
125
|
-
- SHOW DYNAMIC TABLE REFRESH HISTORY
|
|
126
|
-
- DESC HISTORY
|
|
127
|
-
- information_schema.materialized_view_refresh_history
|
|
124
|
+
- **refresh-history-guide.md** — 3 ways to query refresh history
|
|
125
|
+
- SHOW DYNAMIC TABLE REFRESH HISTORY: job-level info, includes refresh_mode (INCREMENTAL/FULL/NO_DATA)
|
|
126
|
+
- DESC HISTORY: version-level history, includes row count, bytes, operation type
|
|
127
|
+
- information_schema.materialized_view_refresh_history: batch analysis, monitoring, CRU statistics
|
|
128
128
|
|
|
129
|
-
|
|
130
|
-
- "
|
|
131
|
-
- "
|
|
132
|
-
- "
|
|
133
|
-
- "
|
|
134
|
-
- "
|
|
129
|
+
**Applicable questions:**
|
|
130
|
+
- "What is the difference between static partition DT and dynamic partition DT?"
|
|
131
|
+
- "What SQL syntax does Dynamic Table support?"
|
|
132
|
+
- "What configuration options are available for incremental computation?"
|
|
133
|
+
- "How do I view the refresh history of a Dynamic Table?"
|
|
134
|
+
- "What triggers a full refresh?"
|
|
135
135
|
|
|
136
136
|
---
|
|
137
137
|
|
|
138
|
-
### dynamic-table-alter/ —
|
|
138
|
+
### dynamic-table-alter/ — Dynamic Table Modification Guide
|
|
139
139
|
|
|
140
|
-
|
|
141
|
-
-
|
|
142
|
-
- 5
|
|
143
|
-
- 5
|
|
144
|
-
-
|
|
145
|
-
-
|
|
140
|
+
**Contents:**
|
|
141
|
+
- Complete Dynamic Table modification workflow (10 operation types)
|
|
142
|
+
- 5 direct ALTER operations: suspend, resume, set_comment, rename_column, set_column_comment
|
|
143
|
+
- 5 CREATE OR REPLACE operations: add_column, drop_column, alter_column, set_refresh_interval, set_select
|
|
144
|
+
- Platform-specific syntax and limitations (CHANGE COLUMN, RENAME COLUMN, DML restrictions, etc.)
|
|
145
|
+
- Detailed examples and troubleshooting
|
|
146
146
|
|
|
147
|
-
> ⚠️
|
|
147
|
+
> ⚠️ This directory corresponds to the independent **dynamic-table-alter sub-skill**. When the user has a clear modification intent, load that sub-skill directly rather than this guide.
|
|
148
148
|
|
|
149
149
|
---
|
|
150
150
|
|
|
151
|
-
### sql-to-dt/ — SQL
|
|
151
|
+
### sql-to-dt/ — SQL to DT Automatic Conversion
|
|
152
152
|
|
|
153
|
-
|
|
153
|
+
Fully automatically converts CREATE TABLE DDL + INSERT OVERWRITE from Hive/Spark or any batch processing system into Dynamic Table DDL and companion files (refresh, prev_refresh, backfill).
|
|
154
154
|
|
|
155
|
-
|
|
155
|
+
See the sql-to-dt sub-skill for detailed conversion rules.
|
|
156
156
|
|
|
157
157
|
---
|
|
158
158
|
|
|
159
|
-
### best-practices/ —
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
- **performance-optimization.md** —
|
|
164
|
-
-
|
|
165
|
-
- SQL
|
|
166
|
-
-
|
|
167
|
-
|
|
168
|
-
- **dimension-table-join-guide.md** —
|
|
169
|
-
-
|
|
170
|
-
-
|
|
171
|
-
-
|
|
172
|
-
-
|
|
173
|
-
-
|
|
174
|
-
|
|
175
|
-
- **non-partitioned-merge-into-warning.md** —
|
|
176
|
-
-
|
|
177
|
-
-
|
|
178
|
-
-
|
|
179
|
-
|
|
180
|
-
- **scheduling-guide.md** —
|
|
181
|
-
-
|
|
182
|
-
-
|
|
183
|
-
- DDL
|
|
184
|
-
- Studio Task
|
|
185
|
-
-
|
|
186
|
-
|
|
187
|
-
|
|
188
|
-
- "
|
|
189
|
-
- "
|
|
190
|
-
- "
|
|
191
|
-
- "
|
|
192
|
-
- "
|
|
193
|
-
- "
|
|
159
|
+
### best-practices/ — Best Practices & Pitfall Guide
|
|
160
|
+
|
|
161
|
+
**Contents:**
|
|
162
|
+
|
|
163
|
+
- **performance-optimization.md** — Performance optimization strategies
|
|
164
|
+
- Core principles: change ratio (< 5% is suitable for incremental), operator types (INNER JOIN faster than OUTER JOIN), data locality
|
|
165
|
+
- SQL optimization tips: prefer INNER JOIN, reduce DISTINCT, window functions must have PARTITION BY, use partition conditions to limit data range
|
|
166
|
+
- Pipeline splitting: break complex DTs into multiple stages
|
|
167
|
+
|
|
168
|
+
- **dimension-table-join-guide.md** — Dimension table JOIN scenarios in detail
|
|
169
|
+
- Core mechanism: dimension table changes are ignored; only fact table changes trigger incremental computation
|
|
170
|
+
- Configuration: TBLPROPERTIES('mv_const_tables'='dim1,dim2') or Session configuration
|
|
171
|
+
- Recommended scenarios: lookup/dictionary tables, T+1 dimension + real-time fact table, large fact JOIN small dimension
|
|
172
|
+
- Not recommended: frequently updated dimensions requiring real-time consistency
|
|
173
|
+
- Data correction: must use full refresh after dimension table changes
|
|
174
|
+
|
|
175
|
+
- **non-partitioned-merge-into-warning.md** — Non-partitioned DT + continuous write risk alert
|
|
176
|
+
- Trigger conditions: DT is non-partitioned + source table has continuous writes + SQL contains ROW_NUMBER() deduplication
|
|
177
|
+
- Three risks: unbounded storage growth, archiving causes performance disaster, cannot filter archive-generated deletes
|
|
178
|
+
- Recommended alternative: MERGE INTO + Table Stream (archive-immune, independent lifecycle management)
|
|
179
|
+
|
|
180
|
+
- **scheduling-guide.md** — Scheduling method selection guide
|
|
181
|
+
- Comparison of two methods: DDL built-in scheduling (REFRESH INTERVAL) vs Studio Task scheduling
|
|
182
|
+
- Always recommend Studio Task when Studio is available: supports upstream/downstream dependencies, unified alerts, visual monitoring
|
|
183
|
+
- Drawbacks of DDL built-in scheduling: no alerts, no dependency orchestration, refresh status can only be checked via manual SQL
|
|
184
|
+
- Studio Task configuration: must enable self-dependency, configure failure/timeout alerts, configure upstream dependencies as needed
|
|
185
|
+
- Scheduling orchestration for multi-level DT pipelines
|
|
186
|
+
|
|
187
|
+
**Applicable questions:**
|
|
188
|
+
- "How do I optimize Dynamic Table performance?"
|
|
189
|
+
- "How do I configure dimension table JOIN?"
|
|
190
|
+
- "What are the risks of non-partitioned Dynamic Tables?"
|
|
191
|
+
- "When should I not use Dynamic Tables?"
|
|
192
|
+
- "Should I use REFRESH INTERVAL or Studio Task for Dynamic Table scheduling?"
|
|
193
|
+
- "How do I receive alerts when a Dynamic Table refresh fails?"
|
|
194
194
|
|
|
195
195
|
---
|
|
196
196
|
|
|
197
|
-
##
|
|
197
|
+
## Routing Decision Tree
|
|
198
198
|
|
|
199
199
|
```
|
|
200
|
-
|
|
200
|
+
User question
|
|
201
201
|
│
|
|
202
|
-
├─
|
|
203
|
-
│
|
|
204
|
-
│ └─
|
|
202
|
+
├─ Contains modification keywords?
|
|
203
|
+
│ ("modify dynamic table", "add column", "change interval", "suspend", "ALTER DYNAMIC TABLE")
|
|
204
|
+
│ └─ Yes → immediately load dynamic-table-alter sub-skill
|
|
205
205
|
│
|
|
206
|
-
├─
|
|
207
|
-
│
|
|
208
|
-
│ └─
|
|
206
|
+
├─ Contains SQL conversion keywords?
|
|
207
|
+
│ ("convert to DT", "sql to dt", "INSERT OVERWRITE to DT", "DDL conversion", "create dynamic table")
|
|
208
|
+
│ └─ Yes → immediately load sql-to-dt sub-skill
|
|
209
209
|
│
|
|
210
|
-
└─
|
|
211
|
-
|
|
212
|
-
└─
|
|
210
|
+
└─ General consultation/learning?
|
|
211
|
+
("how to use dynamic table", "best practices", "performance optimization", "incremental config")
|
|
212
|
+
└─ Yes → provide reference documents from this guide
|
|
213
213
|
```
|
|
214
214
|
|
|
215
215
|
---
|
|
216
216
|
|
|
217
|
-
##
|
|
217
|
+
## Usage Recommendations
|
|
218
218
|
|
|
219
|
-
1.
|
|
220
|
-
2.
|
|
221
|
-
3.
|
|
222
|
-
4.
|
|
223
|
-
5.
|
|
219
|
+
1. **First-time learning**: start with dt-creator/ to understand DT declaration strategies and configuration options
|
|
220
|
+
2. **Migration scenarios**: use the sql-to-dt sub-skill to bulk-convert existing ETL
|
|
221
|
+
3. **Day-to-day operations**: use the dynamic-table-alter sub-skill to modify DT structure
|
|
222
|
+
4. **Performance tuning**: refer to optimization recommendations and pitfall guides in best-practices/
|
|
223
|
+
5. **Scheduling configuration**: always use Studio Task scheduling when Studio is available; refer to best-practices/scheduling-guide.md
|
|
224
224
|
|
|
225
225
|
---
|
|
226
226
|
|
|
227
|
-
##
|
|
227
|
+
## Related Skills
|
|
228
228
|
|
|
229
|
-
- **dynamic-table-alter** —
|
|
230
|
-
- **sql-to-dt** — SQL
|
|
229
|
+
- **dynamic-table-alter** — Operational sub-skill for modifying Dynamic Tables (10 modification operation types)
|
|
230
|
+
- **sql-to-dt** — Conversion sub-skill for SQL to DT (6-step automatic conversion workflow)
|