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

   ### What changes were proposed in this PR?
   
   Pin behavior of three previously-untested file scan source descriptors in 
`common/workflow-operator`. No production-code changes.
   
   | Spec | Source class | Tests |
   | --- | --- | --- |
   | `CSVOldScanSourceOpDescSpec` | `CSVOldScanSourceOpDesc` | 6 |
   | `JSONLScanSourceOpDescSpec` | `JSONLScanSourceOpDesc` | 5 |
   | `ArrowSourceOpDescSpec` | `ArrowSourceOpDesc` | 5 |
   
   **Behavior pinned**
   
   | Surface | Contract |
   | --- | --- |
   | `operatorInfo` | exact name + description; Data Input group; 0 inputs / 1 
output |
   | field defaults | per-type defaults (CSVOld `customDelimiter=Some(",")`, 
`hasHeader=true`; JSONL `flatten=false`; encoding `UTF_8`; `limit`/`offset` 
`None`; `fileTypeName`) |
   | `sourceSchema()` | `null` before a file is resolved (IO-free 
short-circuit) |
   | `getPhysicalOp` | wires `OpExecWithClassName` for the matching `*OpExec`, 
no input port / one output port, IO-free; CSVOld falls back to a comma on an 
empty delimiter; JSONL is parallelizable |
   | Round-trip | config fields preserved through the polymorphic `LogicalOp` 
base |
   
   ### Any related issues, documentation, discussions?
   
   Part of the ongoing `workflow-operator` unit-test coverage effort (follow-up 
to #5843, #5844).
   
   ### How was this PR tested?
   
   - `sbt "WorkflowOperator/testOnly *CSVOldScanSourceOpDescSpec 
*JSONLScanSourceOpDescSpec *ArrowSourceOpDescSpec"` — 16 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])
   


-- 
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