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

   ## What are the changes?
   
   A page for contributors adding an operator, covering what the existing Java 
and Python guides do not: declaring the output schema, stating a constraint on 
every config property, writing the standalone Python fragment the exporter 
needs, getting a green verification run, and recording a run that cannot 
happen. Two diagrams carry the shape of the translation and of the two compared 
paths.
   
   Part of #8325, 22 of 22; that issue lists the set in order.
   Closes #8458, the task this change is the whole of.
   
   ## Why are the changes needed?
   
   The two implementation guides stop at the operator's own logic. Everything a 
new operator has to satisfy afterwards was spread across code comments and had 
to be learned by having a review point it out. `getOutputSchemas` in particular 
appears in neither existing guide, although every operator must implement it, 
and a schema that disagrees with what the executor emits fails at run time 
rather than at compile time.
   
   Each rule here was read out of the code rather than recalled, which 
corrected three things a reader would otherwise have been told wrong: numeric 
bounds come from a field's `@JsonSchemaInject`, not from `@Min` and `@Max`, 
which nothing in the repository uses and whose upper bound the configuration 
generator never reads; a `pattern` is read both by the browser and by that 
generator, and only the second matches whole strings; and `WCS_TEST_FILTER` is 
how CI splits its two jobs, not something a local run sets.
   
   ## Does this PR introduce any user-facing change?
   
   No. Documentation only.
   
   ## Was this patch authored or co-authored with 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]

Reply via email to