kz930 opened a new pull request, #8317: URL: https://github.com/apache/texera/pull/8317
### What changes were proposed in this PR? Three of the four Hugging Face operators read their column as text and hand it to a tokenizer, which takes a string and nothing else. The fourth standardizes two petal measurements and hands them to the model as floats. None of the four said so, so the form accepted a column of any type and said nothing until the run failed, inside the tokenizer, with a message naming neither the operator nor the column. Each operator now carries a class-level `@JsonSchemaInject` naming the types its column picker will take: `string` for the `attribute` of Sentiment Analysis, Spam Detection and Text Summarization, and `integer` / `long` / `double` for Iris Logistic Regression's two petal fields. The frontend turns a rule into a message naming the column, its type and the type expected, so a wrong-typed column is now answered while the operator is being configured rather than part-way through a run. No generated Python changes. ### Any related issues, documentation, discussions? Closes #8316. ### How was this PR tested? Each operator's own spec gains a test reading the annotation's payload, the same shape `UrlVizOpDescSpec` and the other constrained operators use. `AttributeTypeRuleTargetSpec`, which checks that every rule names a real property, now covers these four. `WorkflowOperator/testOnly *HuggingFace*Spec *AttributeTypeRuleTargetSpec` passes: 275 tests. ### Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Code (Claude Opus 5) -- 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]
