Skip to content

test: support captured runtime values in SQL cases - #202

Merged
slyunnn merged 3 commits into
matrixorigin:mainfrom
slyunnn:test/pitr-restore-capture
Aug 26, 2026
Merged

test: support captured runtime values in SQL cases#202
slyunnn merged 3 commits into
matrixorigin:mainfrom
slyunnn:test/pitr-restore-capture

Conversation

@slyunnn

@slyunnn slyunnn commented Aug 26, 2026

Copy link
Copy Markdown
Collaborator

Adds @capture:name for scalar runtime values used by later {{name}} placeholders. This enables a deterministic PITR restore test without unsupported prepared RESTORE statements.\n\nValidation: mvn -Dtest=ScriptParserTest test; local PITR restore case 17/17.

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@slyunnn
slyunnn marked this pull request as draft August 26, 2026 03:35
@slyunnn
slyunnn marked this pull request as ready for review August 26, 2026 03:36
@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@slyunnn
slyunnn requested a review from Ariznawlll August 26, 2026 03:37

@Ariznawlll Ariznawlll left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Requesting changes for one fail-closed issue in the new capture control path. The parser tests and the full unit suite pass on JDK 8, but there is no execution-level test covering this failure boundary.

Comment thread src/main/java/io/mo/db/Executor.java

@Ariznawlll Ariznawlll left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original fail-closed behavior is now implemented, but this head is not merge-ready: the new execution test does not compile on the repository-required JDK 8, and the genRS capture-failure early return bypasses statement/result-set and test-database cleanup.

Comment thread src/test/java/io/mo/db/ExecutorCaptureTest.java Outdated
Comment thread src/main/java/io/mo/db/Executor.java Outdated

@Ariznawlll Ariznawlll left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Re-reviewed head 74732b9. The previous blockers are addressed: capture failures now fail closed in both run and genRS; genRS routes failures through statement/result-set and test-database cleanup; the JDK 8 character literal is valid; and execution tests cover query-error, empty-result, and NULL-result cleanup. I also ran the full Maven unit suite locally with Java compilation targeting 1.8: 74 tests passed. Non-blocking follow-up: the current GitHub CI jobs execute the checked-in prebuilt mo-tester JAR and do not compile or run tests from src/, so adding an explicit Maven build/test job would make future Java-source PR checks meaningful.

@slyunnn
slyunnn merged commit adf67c6 into matrixorigin:main Aug 26, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants