Appearance
Detector catalog / SQL plans
PLAN
Cast on a join key
A cast on a join key forces another shuffle.
- Outcome
- SQL plans
- Scope
- Judged per SQL query
- Usual fix
- A change in the job code
- CI gate
- No budget flag: gate it with
--fail-on-introducedagainst a baseline
An example finding
Where you see it
Dashboard
The PLAN tag marks it in the action region of the dashboard, among the widgets that rank a fix. How to read it in the findings guide.
Agent (MCP)
An assistant can read this entry with the list_detectors tool and its background with get_finding_documentation. The call and the response below come from a real run of the MCP server.
Call
{
"tool": "list_detectors",
"arguments": {
"type": "joinKeyCast"
}
}Response
{
"count": 1,
"detectors": [
{
"type": "joinKeyCast",
"name": "cast on a join key",
"tag": "PLAN",
"tagSharedWith": [
"duplicatePlanSubtree",
"smallFiles",
"overBroadcast",
"underBroadcast",
"pythonUdf",
"nestedLoopJoin",
"mergeRewrite",
"unprunedScan"
],
"family": "plan",
"pitch": "A cast on a join key forces another shuffle.",
"region": "action",
"scope": "sql",
"fixEffort": "code",
"thresholdSummary": "a shuffled join with a cast in its key, followed by an exchange on the uncast column",
"detectors": [
{
"detector": "joinKeyCast",
"version": 1,
"thresholds": {}
}
],
"pages": {
"catalog": "docs/detectors/joinKeyCast.html",
"guide": "docs/user-guide/understanding-findings.html#plan"
},
"tuning": {
"kind": "chapter",
"anchor": "#joins",
"path": "docs/tuning-reference/joins.html#joins"
},
"gate": null
}
]
}get_finding_documentation call
{
"tool": "get_finding_documentation",
"arguments": {
"type": "joinKeyCast"
}
}Its response, with each Markdown body replaced by its length
{
"type": "joinKeyCast",
"name": "Cast On A Join Key",
"detectionDoc": {
"tag": "PLAN",
"title": "Plan advisor",
"content": "<7876 characters of Markdown>"
},
"tuningDoc": {
"anchor": "#joins",
"title": "Join Optimization",
"content": "<12010 characters of Markdown>"
}
}CI (CLI)
List this entry from the command line. The output below is a real run of the command. Budgets and exit codes are in the CI guide.
sparkforensics-analyze detectors --type joinKeyCast --format md# Detectors (1)
## SQL plans
| Tag | Type | Scope | Fix | Gate | What it finds |
| --- | --- | --- | --- | --- | --- |
| PLAN | `joinKeyCast` | sql | code | | A cast on a join key forces another shuffle. |
Report only this finding type for a run with --type:
sparkforensics-analyze <event-log> --type joinKeyCast --impact critical,warning,info It has no budget flag. Fail a build on a new one by comparing against a baseline with --fail-on-introduced.
Airflow
The operator has no budget parameter for it. Use fail_on_introduced with a baseline.
check_spark_job = SparkForensicsOperator(
task_id="check_spark_job",
log_source=...,
backend=SubprocessAnalyzeHook(),
baseline_log_source=...,
fail_on_introduced="critical",
)The operator works per run, and its summary counts findings per impact band. See the operator for its parameters.
How it is measured
Thresholds
A shuffled join with a cast in its key, followed by an exchange on the uncast column.
joinKeyCast version 1
| Threshold | Default |
|---|---|
| No thresholds. | |
Each rule's impact bands and fixed fallbacks are in the threshold tables.
Override a default per run with --thresholds; see Tuning detector thresholds.
Docs
- This finding is covered in a general tuning chapter: Spark tuning reference.
- Findings guide: PLAN in Understanding findings.
- Shares the PLAN tag with: duplicate plan subtree, small files, oversized broadcast join, missed broadcast join, row-at-a-time Python UDF, nested loop join, MERGE rewrite, unpruned partitioned scan.