Assertion JiT integration by rafal-hawrylak · Pull Request #2223 · dataform-co/dataform

rafal-hawrylak · 2026-07-15T14:11:21Z

Assertion actions were not integrated into the JiT compilation runtime, even though the compiler (core/jit_compiler.ts) already supports them. Two gaps in Runner:

compileJitAction had no branch for action.type === "assertion", so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected the request.
createTasksFromJitResponse had no branch for jitResponse.assertion, so even a successful compile produced zero tasks and the action silently did nothing.

This PR wires both - assertions with jitCode now compile through the JiT worker and produce the same task set as their AoT counterparts (via executionSql.createAssertionTasks).

ikholopov-omni · 2026-07-15T15:03:03Z

Is this PR rebased onto any other PRs?

If yes - please send to review after those are merged.

Runner.compileJitAction was missing an assertion branch in the target-type selector, so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected them. createTasksFromJitResponse also had no branch for jitResponse.assertion, so the compiled query never reached executionSql.createAssertionTasks. Wire both: select ASSERTION for assertion actions, and hydrate a dataform.Assertion from the JiT response before building tasks. Tests: - Runner-level unit test (jit_run_test.ts) drives a single JiT assertion action end-to-end and checks the resulting task set. - CLI e2e test (index_jit_runtime_test.ts) uses assert().jitCode() against dry-run BigQuery.

Bumps the npm package version to release the `PropertyGraph` action (#2243, #2246, #2249) and JiT assertion integration (#2185, #2223).

rafal-hawrylak · 2026-07-15T14:11:21Z

Assertion actions were not integrated into the JiT compilation runtime, even though the compiler (core/jit_compiler.ts) already supports them. Two gaps in Runner:

compileJitAction had no branch for action.type === "assertion", so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected the request.
createTasksFromJitResponse had no branch for jitResponse.assertion, so even a successful compile produced zero tasks and the action silently did nothing.

This PR wires both - assertions with jitCode now compile through the JiT worker and produce the same task set as their AoT counterparts (via executionSql.createAssertionTasks).

ikholopov-omni · 2026-07-15T15:03:03Z

Is this PR rebased onto any other PRs?

If yes - please send to review after those are merged.

Runner.compileJitAction was missing an assertion branch in the target-type selector, so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected them. createTasksFromJitResponse also had no branch for jitResponse.assertion, so the compiled query never reached executionSql.createAssertionTasks. Wire both: select ASSERTION for assertion actions, and hydrate a dataform.Assertion from the JiT response before building tasks. Tests: - Runner-level unit test (jit_run_test.ts) drives a single JiT assertion action end-to-end and checks the resulting task set. - CLI e2e test (index_jit_runtime_test.ts) uses assert().jitCode() against dry-run BigQuery.

Bumps the npm package version to release the `PropertyGraph` action (#2243, #2246, #2249) and JiT assertion integration (#2185, #2223).

rafal-hawrylak · 2026-07-15T14:11:21Z

Assertion actions were not integrated into the JiT compilation runtime, even though the compiler (core/jit_compiler.ts) already supports them. Two gaps in Runner:

compileJitAction had no branch for action.type === "assertion", so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected the request.
createTasksFromJitResponse had no branch for jitResponse.assertion, so even a successful compile produced zero tasks and the action silently did nothing.

This PR wires both - assertions with jitCode now compile through the JiT worker and produce the same task set as their AoT counterparts (via executionSql.createAssertionTasks).

ikholopov-omni · 2026-07-15T15:03:03Z

Is this PR rebased onto any other PRs?

If yes - please send to review after those are merged.

Runner.compileJitAction was missing an assertion branch in the target-type selector, so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected them. createTasksFromJitResponse also had no branch for jitResponse.assertion, so the compiled query never reached executionSql.createAssertionTasks. Wire both: select ASSERTION for assertion actions, and hydrate a dataform.Assertion from the JiT response before building tasks. Tests: - Runner-level unit test (jit_run_test.ts) drives a single JiT assertion action end-to-end and checks the resulting task set. - CLI e2e test (index_jit_runtime_test.ts) uses assert().jitCode() against dry-run BigQuery.

Bumps the npm package version to release the `PropertyGraph` action (#2243, #2246, #2249) and JiT assertion integration (#2185, #2223).

rafal-hawrylak · 2026-07-15T14:11:21Z

Assertion actions were not integrated into the JiT compilation runtime, even though the compiler (core/jit_compiler.ts) already supports them. Two gaps in Runner:

compileJitAction had no branch for action.type === "assertion", so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected the request.
createTasksFromJitResponse had no branch for jitResponse.assertion, so even a successful compile produced zero tasks and the action silently did nothing.

This PR wires both - assertions with jitCode now compile through the JiT worker and produce the same task set as their AoT counterparts (via executionSql.createAssertionTasks).

ikholopov-omni · 2026-07-15T15:03:03Z

Is this PR rebased onto any other PRs?

If yes - please send to review after those are merged.

Runner.compileJitAction was missing an assertion branch in the target-type selector, so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected them. createTasksFromJitResponse also had no branch for jitResponse.assertion, so the compiled query never reached executionSql.createAssertionTasks. Wire both: select ASSERTION for assertion actions, and hydrate a dataform.Assertion from the JiT response before building tasks. Tests: - Runner-level unit test (jit_run_test.ts) drives a single JiT assertion action end-to-end and checks the resulting task set. - CLI e2e test (index_jit_runtime_test.ts) uses assert().jitCode() against dry-run BigQuery.

Bumps the npm package version to release the `PropertyGraph` action (#2243, #2246, #2249) and JiT assertion integration (#2185, #2223).

rafal-hawrylak · 2026-07-15T14:11:21Z

Assertion actions were not integrated into the JiT compilation runtime, even though the compiler (core/jit_compiler.ts) already supports them. Two gaps in Runner:

compileJitAction had no branch for action.type === "assertion", so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected the request.
createTasksFromJitResponse had no branch for jitResponse.assertion, so even a successful compile produced zero tasks and the action silently did nothing.

This PR wires both - assertions with jitCode now compile through the JiT worker and produce the same task set as their AoT counterparts (via executionSql.createAssertionTasks).

ikholopov-omni · 2026-07-15T15:03:03Z

Is this PR rebased onto any other PRs?

If yes - please send to review after those are merged.

Runner.compileJitAction was missing an assertion branch in the target-type selector, so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected them. createTasksFromJitResponse also had no branch for jitResponse.assertion, so the compiled query never reached executionSql.createAssertionTasks. Wire both: select ASSERTION for assertion actions, and hydrate a dataform.Assertion from the JiT response before building tasks. Tests: - Runner-level unit test (jit_run_test.ts) drives a single JiT assertion action end-to-end and checks the resulting task set. - CLI e2e test (index_jit_runtime_test.ts) uses assert().jitCode() against dry-run BigQuery.

Bumps the npm package version to release the `PropertyGraph` action (#2243, #2246, #2249) and JiT assertion integration (#2185, #2223).

rafal-hawrylak · 2026-07-15T14:11:21Z

Assertion actions were not integrated into the JiT compilation runtime, even though the compiler (core/jit_compiler.ts) already supports them. Two gaps in Runner:

compileJitAction had no branch for action.type === "assertion", so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected the request.
createTasksFromJitResponse had no branch for jitResponse.assertion, so even a successful compile produced zero tasks and the action silently did nothing.

This PR wires both - assertions with jitCode now compile through the JiT worker and produce the same task set as their AoT counterparts (via executionSql.createAssertionTasks).

ikholopov-omni · 2026-07-15T15:03:03Z

Is this PR rebased onto any other PRs?

If yes - please send to review after those are merged.

Runner.compileJitAction was missing an assertion branch in the target-type selector, so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected them. createTasksFromJitResponse also had no branch for jitResponse.assertion, so the compiled query never reached executionSql.createAssertionTasks. Wire both: select ASSERTION for assertion actions, and hydrate a dataform.Assertion from the JiT response before building tasks. Tests: - Runner-level unit test (jit_run_test.ts) drives a single JiT assertion action end-to-end and checks the resulting task set. - CLI e2e test (index_jit_runtime_test.ts) uses assert().jitCode() against dry-run BigQuery.

Bumps the npm package version to release the `PropertyGraph` action (#2243, #2246, #2249) and JiT assertion integration (#2185, #2223).

rafal-hawrylak · 2026-07-15T14:11:21Z

Assertion actions were not integrated into the JiT compilation runtime, even though the compiler (core/jit_compiler.ts) already supports them. Two gaps in Runner:

compileJitAction had no branch for action.type === "assertion", so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected the request.
createTasksFromJitResponse had no branch for jitResponse.assertion, so even a successful compile produced zero tasks and the action silently did nothing.

This PR wires both - assertions with jitCode now compile through the JiT worker and produce the same task set as their AoT counterparts (via executionSql.createAssertionTasks).

ikholopov-omni · 2026-07-15T15:03:03Z

Is this PR rebased onto any other PRs?

If yes - please send to review after those are merged.

Runner.compileJitAction was missing an assertion branch in the target-type selector, so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected them. createTasksFromJitResponse also had no branch for jitResponse.assertion, so the compiled query never reached executionSql.createAssertionTasks. Wire both: select ASSERTION for assertion actions, and hydrate a dataform.Assertion from the JiT response before building tasks. Tests: - Runner-level unit test (jit_run_test.ts) drives a single JiT assertion action end-to-end and checks the resulting task set. - CLI e2e test (index_jit_runtime_test.ts) uses assert().jitCode() against dry-run BigQuery.

Bumps the npm package version to release the `PropertyGraph` action (#2243, #2246, #2249) and JiT assertion integration (#2185, #2223).

rafal-hawrylak · 2026-07-15T14:11:21Z

Assertion actions were not integrated into the JiT compilation runtime, even though the compiler (core/jit_compiler.ts) already supports them. Two gaps in Runner:

compileJitAction had no branch for action.type === "assertion", so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected the request.
createTasksFromJitResponse had no branch for jitResponse.assertion, so even a successful compile produced zero tasks and the action silently did nothing.

This PR wires both - assertions with jitCode now compile through the JiT worker and produce the same task set as their AoT counterparts (via executionSql.createAssertionTasks).

ikholopov-omni · 2026-07-15T15:03:03Z

Is this PR rebased onto any other PRs?

If yes - please send to review after those are merged.

Runner.compileJitAction was missing an assertion branch in the target-type selector, so assertions fell through to JIT_COMPILATION_TARGET_TYPE_UNSPECIFIED and the compiler rejected them. createTasksFromJitResponse also had no branch for jitResponse.assertion, so the compiled query never reached executionSql.createAssertionTasks. Wire both: select ASSERTION for assertion actions, and hydrate a dataform.Assertion from the JiT response before building tasks. Tests: - Runner-level unit test (jit_run_test.ts) drives a single JiT assertion action end-to-end and checks the resulting task set. - CLI e2e test (index_jit_runtime_test.ts) uses assert().jitCode() against dry-run BigQuery.

Bumps the npm package version to release the `PropertyGraph` action (#2243, #2246, #2249) and JiT assertion integration (#2185, #2223).

rafal-hawrylak requested review from apilaskowski and ikholopov-omni July 15, 2026 14:11

rafal-hawrylak requested a review from a team as a code owner July 15, 2026 14:11

rafal-hawrylak requested review from krushangSk17 and removed request for a teamJuly 15, 2026 14:11

rafal-hawrylak mentioned this pull request Jul 15, 2026
Integrate JiT compilation into CLI #2110
Closed

ikholopov-omni removed request for apilaskowski and krushangSk17 July 15, 2026 15:03

rafal-hawrylak force-pushed the assertion-jit-integration branch 3 times, most recently from 5efa010 to 2708c15Compare July 16, 2026 07:34

rafal-hawrylak force-pushed the assertion-jit-integration branch from 2708c15 to 88a88c7Compare July 22, 2026 20:08

rafal-hawrylak force-pushed the assertion-jit-integration branch from 88a88c7 to 160c6a7Compare August 5, 2026 17:59

rafal-hawrylak force-pushed the assertion-jit-integration branch from 160c6a7 to 6594e90Compare August 18, 2026 21:08

ikholopov-omni approved these changes Aug 19, 2026
View reviewed changes

rafal-hawrylak merged commit 21830c2 into mainAug 19, 2026
11 checks passed

rafal-hawrylak deleted the assertion-jit-integration branch August 19, 2026 08:43

rafal-hawrylak mentioned this pull request Aug 19, 2026
Bump DF_VERSION from 3.0.64 to 3.0.65 #2250
Merged

apilaskowski pushed a commit that referenced this pull request Aug 19, 2026
Bump DF_VERSION from 3.0.64 to 3.0.65 (#2250)
cb5ae34
Bumps the npm package version to release the `PropertyGraph` action (#2243, #2246, #2249) and JiT assertion integration (#2185, #2223).