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: 9c645499cd00b96464bf509b1041413b3fa1f8bb / kary zheng <[email protected]> docs: correct two rules that writing an operator disproved The page said to implement `getOutputSchemas`. That is the Python operator's way; a Java or Scala one declares its output through a `SchemaPropagationFunc` inside `getPhysicalOp`, which is what 32 of the registered operators do. And escaping has a second half. A `pyb` field has to reach the template whole, so joining it to anything in Scala first defeats it — the protected value is handed over as a plain string, and the placeholder leaks into the emitted Python. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> Report URL: https://github.com/apache/texera/actions/runs/34422193244 With regards, GitHub Actions via GitBox
