Skip to content

Verify production CTAS with the default write setting - #267

Closed
KirillKurdyukov wants to merge 3 commits into
mainfrom
codex/c03-default-write-mode
Closed

KirillKurdyukov wants to merge 3 commits into
mainfrom
codex/c03-default-write-mode

Conversation

@KirillKurdyukov

@KirillKurdyukov KirillKurdyukov commented Sep 29, 2026 •

Copy link
Copy Markdown
Collaborator

Verify production adapter CTAS with insert.non-transactional-insert.enabled=false: successful table creation and duplicate-key failure cleanup. Document the separate limitation of ordinary INSERT in this default mode and the direct, non-transactional setting with its partial-write risk.

The diagnostic INSERT error test has been removed at the user's request. The retained test covers CTAS and cleanup only. No production code, capabilities, workflows, or skips change.

Validation for 23238991856156897f33107258e8d549c9cb7364: JDK 25 test compilation and diff checks passed; independent GPT-6 Astra/high review found no issues. Full ordinary CI36577034854 passed: 313 total, 228 passed, 85 skipped, zero failures/errors. The retained default-write-mode class passed both its CTAS test and framework check.

The INSERT limitation was observed against real YDB in diagnostic CI36566451734: Trino 483's CREATE TABLE tmp AS SELECT ... WHERE 0 = 1 staging statement was rejected at AS. This PR does not implement transactional INSERT or expand inherited capabilities.

@KirillKurdyukov KirillKurdyukov changed the title Verify YDB writes with the default insert mode Document and verify the default YDB insert limitation Sep 29, 2026
@KirillKurdyukov KirillKurdyukov changed the title Document and verify the default YDB insert limitation Verify production CTAS with the default write setting Sep 29, 2026
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.

1 participant