GitHub user mengw15 added a comment to the discussion: Per-user warehouses are feature-complete behind a flag; proposing to turn it on
Two things. **The prompt-to-create flow** mirrors the computing-unit path deliberately — the same shape as "Connect" when no unit exists. Building it surfaced a real bug on the computing-unit side, where that button could not actually be clicked; #8590 fixed it, so both behave the same way now. **On risk.** The resolver is unit-tested in both flag states, the ordering rule is pinned, and the tab, picker and agent chain have suites at both ends; I also ran the whole feature by hand against a local deployment with the flag on, live Lakekeeper and MinIO — that is the recording. The PR that flips the flag runs the whole suite with the feature on, so anything the tests can catch shows up before it merges. My preference is to turn it on in `main` and raise issues for whatever surfaces. The feature is additive and reversible — nothing is migrated, results written before the flip stay readable, and turning it back off refuses explicitly rather than silently returning "table not found". `main` is where this should surface; releases are cut from release branches, so they stay stable regardless. GitHub link: https://github.com/apache/texera/discussions/8633#discussioncomment-18545966 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
