aglinxinyuan opened a new pull request, #5826:
URL: https://github.com/apache/texera/pull/5826

   ### What changes were proposed in this PR?
   
   Pin behavior of three previously-untested single-input transform descriptors 
in `common/workflow-operator/`. No production-code changes.
   
   | Spec | Source class | Tests |
   | --- | --- | --- |
   | `TypeCastingOpDescSpec` | `TypeCastingOpDesc` | 5 |
   | `UnnestStringOpDescSpec` | `UnnestStringOpDesc` | 5 |
   | `SpecializedFilterOpDescSpec` | `SpecializedFilterOpDesc` | 4 |
   
   All three spec files follow the `<srcClassName>Spec.scala` one-to-one 
convention.
   
   **Behavior pinned**
   
   | Surface | Contract |
   | --- | --- |
   | `operatorInfo` | exact name + group (`Type Casting`/`Unnest 
String`/`Filter`); `Filter` advertises `supportReconfiguration` |
   | `getPhysicalOp` wiring | `OpExecWithClassName` with the exact executor 
FQCN; port **identities** carried forward (`keySet`) |
   | `TypeCasting` schema propagation | empty units = identity; a cast unit 
changes the target column's type; casting-unit round-trip |
   | `UnnestString` schema propagation | non-blank `resultAttribute` appends a 
STRING column; blank `resultAttribute` throws |
   | `SpecializedFilter` | `predicates` default empty; round-trip |
   
   ### Any related issues, documentation, discussions?
   
   Closes #5823.
   
   ### How was this PR tested?
   
   Pure unit-test additions; verified locally with:
   
   - `sbt "WorkflowOperator/testOnly 
org.apache.texera.amber.operator.typecasting.TypeCastingOpDescSpec 
org.apache.texera.amber.operator.unneststring.UnnestStringOpDescSpec 
org.apache.texera.amber.operator.filter.SpecializedFilterOpDescSpec"` — 14 
tests, all green
   - `sbt "WorkflowOperator/Test/scalafmtCheck"` and `sbt 
"WorkflowOperator/Test/scalafix --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])


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to