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

   ### What changes were proposed in this PR?
   
   Pin behavior of three previously-untested Sklearn ensemble classifier 
descriptors in `common/workflow-operator`. No production-code changes.
   
   | Spec | Source class | Tests |
   | --- | --- | --- |
   | `SklearnAdaptiveBoostingOpDescSpec` | `SklearnAdaptiveBoostingOpDesc` | 5 |
   | `SklearnBaggingOpDescSpec` | `SklearnBaggingOpDesc` | 5 |
   | `SklearnGradientBoostingOpDescSpec` | `SklearnGradientBoostingOpDesc` | 5 |
   
   **Behavior pinned**
   
   | Surface | Contract |
   | --- | --- |
   | `operatorInfo` | exact model name + `Sklearn <name> Operator` description; 
Sklearn group; training/testing input ports + one blocking output |
   | field defaults | `countVectorizer`/`tfidfTransformer` `false`; 
`target`/`text` `null` |
   | `getOutputSchemas` | `model_name` (STRING) + `model` (BINARY) keyed by the 
declared output port |
   | `generatePythonCode` | imports the matching sklearn estimator and builds 
the `make_pipeline` model |
   | 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 (follow-up 
to the Sklearn Naive Bayes coverage in #5925).
   
   ### How was this PR tested?
   
   - `sbt "WorkflowOperator/testOnly *SklearnAdaptiveBoostingOpDescSpec 
*SklearnBaggingOpDescSpec *SklearnGradientBoostingOpDescSpec"` — 15 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