Skip to content

Run an operator through the engine and keep what it wrote #8408

Description

@kz930

Task Summary

An operator's answer cannot be compared against anything until there is a way to get one. This step adds OpExecHarness: it builds the physical operator a descriptor describes, feeds it the rows of a JSONL file per input port, and writes what each output port produced back out, schema in a sidecar because JSONL carries values alone and cannot say a column is an integer rather than a number.

The tests that need a Python interpreter are tagged and split into a job that provisions one, so the job that does not stays as fast as it was.

Second of the twenty-one steps listed in #8325. It stands on its own: it touches no code from the export itself.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions