The GitHub Actions job "Required Checks" on 
texera.git/gh-readonly-queue/main/pr-5953-18a24e51e60835388e8bec8847520470c01ff55d
 has succeeded.
Run started by GitHub user aglinxinyuan (triggered by aglinxinyuan).

Head commit for run:
ad908b74857b86f4bc6087b61fcbf9a54f738edb / Xinyuan Lin <[email protected]>
test(workflow-operator): add unit test coverage for relational join descriptors 
(CartesianProduct, HashJoin) (#5953)

### What changes were proposed in this PR?

Pin behavior of the two previously-untested relational join descriptors
in `common/workflow-operator`. No production-code changes.

| Spec | Source class | Tests |
| --- | --- | --- |
| `CartesianProductOpDescSpec` | `CartesianProductOpDesc` | 5 |
| `HashJoinOpDescSpec` | `HashJoinOpDesc` | 5 |

**Behavior pinned**

| Surface | Contract |
| --- | --- |
| `operatorInfo` | exact name/description; Join group; left/right 2-in,
1-out shape |
| field defaults | HashJoin `buildAttributeName`/`probeAttributeName`
null, `joinType` `INNER` |
| schema propagation | CartesianProduct concatenates left + right,
renaming right-side duplicates (`k` → `k#@1`); HashJoin drops the probe
key, keeps the build key, and renames retained right-side clashes |
| `getPhysicalOp` | CartesianProduct wires
`OpExecWithClassName(...CartesianProductOpExec)` with the correct ports
|
| Round-trip | config fields preserved through the polymorphic
`LogicalOp` base, with the correct `operatorType` discriminator |

### Any related issues, documentation, discussions?

Part of the ongoing `workflow-operator` unit-test coverage effort.

### How was this PR tested?

- `sbt "WorkflowOperator/testOnly *CartesianProductOpDescSpec
*HashJoinOpDescSpec"` — 10 tests, all green
- `sbt "WorkflowOperator/Test/scalafmtCheck"` and `sbt
"WorkflowOperator/scalafixAll --check"` — clean
- CI to confirm

### Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Opus 4.8 [1M context])

Report URL: https://github.com/apache/texera/actions/runs/28226973770

With regards,
GitHub Actions via GitBox

Reply via email to