The GitHub Actions job "Benchmarks" on texera.git/docs/guide-to-add-a-new-operator has succeeded. Run started by GitHub user kz930 (triggered by kz930).
Head commit for run: 0c9255be116430b0551bff7d43b3b48852b504aa / kary zheng <[email protected]> docs: say what a new operator owes beyond its own code The Java and Python guides cover writing the operator. What they do not cover is everything a new one has to satisfy afterwards: a stated constraint on each config property, the standalone Python fragment the exporter needs, a green verification run, and where to record a run that cannot happen. Written from the code rather than from memory, so it names the mechanisms as they are: bounds come from a field's JsonSchemaInject rather than from Min and Max, which nothing here uses; a pattern is read by the browser and by the verification generator, and only one of the two matches whole strings. Two diagrams carry the shape of the translation and of the two compared paths. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/34313578553 With regards, GitHub Actions via GitBox
