一键导入
recipe-patterns
Use when creating, configuring, or running any Dataiku recipe (prepare, join, group, sync, python) including data cleaning, formulas, and GREL
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Use when creating, configuring, or running any Dataiku recipe (prepare, join, group, sync, python) including data cleaning, formulas, and GREL
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Use when working with data collections, dataset metadata, tags, meanings, or AI-generated descriptions
Use when creating datasets, uploading files, managing schemas, or configuring dataset connections
Use when building datasets, running multi-step pipelines, managing dependencies, or orchestrating recipe execution order
Use when training prediction models, extracting metrics, configuring algorithms, or deploying models
Use when debugging failed jobs, diagnosing errors, or resolving common Dataiku issues
基于 SOC 职业分类
| name | recipe-patterns |
| description | Use when creating, configuring, or running any Dataiku recipe (prepare, join, group, sync, python) including data cleaning, formulas, and GREL |
Reference patterns for creating different recipe types via the Python API.
MANDATORY: Read the relevant reference file before writing any recipe code.
Do NOT rely on general knowledge for GREL functions or API methods. Dataiku GREL differs from OpenRefine GREL and other variants. Always verify function names against the reference.
| Recipe Type | Use When | Key Method |
|---|---|---|
| Prepare | Column transforms, filtering, formula columns, renaming, data cleaning | project.new_recipe("prepare", ...) |
| Join | Combining datasets on key columns (LEFT, INNER, RIGHT, OUTER) | project.new_recipe("join", ...) |
| Group | Aggregations: sum, count, avg, min, max, stddev, etc. | project.new_recipe("grouping", ...) |
| Sync | Copying data between connections (e.g., to a data warehouse) | project.new_recipe("sync", ...) |
| Python | Custom transformations not possible with visual recipes | project.new_recipe("python", ...) |
Every recipe follows the same create-configure-run lifecycle:
# 1. Create via builder
builder = project.new_recipe("<type>", "<recipe_name>")
builder.with_input("<input_dataset>")
builder.with_new_output("<output_dataset>", "<connection>") # creates output dataset
recipe = builder.create()
# 2. Configure settings
settings = recipe.get_settings()
# ... recipe-specific configuration ...
settings.save()
# 3. Apply schema updates
schema_updates = recipe.compute_schema_updates()
if schema_updates.any_action_required():
schema_updates.apply()
# 4. Run and check
job = recipe.run(no_fail=True)
state = job.get_status()["baseStatus"]["state"] # "DONE" or "FAILED"
Always sample the output and verify the result before reporting success. Silent data issues (wrong values, all nulls, unexpected types) are common.
from helpers.export import sample
rows = sample(client, "PROJECT_KEY", "output_dataset", 5)
for r in rows:
print(r)
settings.save() after configuration changescompute_schema_updates().apply() for visual recipesrecipe.run(no_fail=True) to execute (already waits for completion)job.get_status()["baseStatus"]["state"] for "DONE" or "FAILED"Copy-paste patterns that have been validated against a live Dataiku instance:
Recipe types:
add_processor_step() APIset_codeData preparation:
Troubleshooting: