Hi All, Review reminder: Subham updated [3960] with some new changes.
Specifically, this PR separates DDL files into three sections to match independent use cases: MetaStore, Metrics, Events. >From my POV this change is reasonable and will allow Polaris users more control over the RDBMS schema and data depending on their particular deployment preferences. Still, I believe these changes are significant enough to warrant a broader review, so please take a look at the PR. The rationale for splitting the DDL files is covered to some extent by GH comments, but feel free to discuss any related concerns in this email thread too. [3960] https://github.com/apache/polaris/pull/3960 Cheers, Dmitri. On Tue, Mar 10, 2026 at 8:27 AM Subham Sangwan <[email protected]> wrote: > Hi Polaris Dev Team I have opened PR #3960 [1] to introduce the > foundational groundwork for multi-datasource support in JDBC persistence, > addressing Issue #3890 [2].The goal is to enable physical isolation of > different persistence workloads (METASTORE, METRICS, EVENTS) into dedicated > connection pools or databases. This will allow Polaris to better handle > high-traffic environments by preventing "noisy neighbor" effects on the > core entity tables. > > Key Highlights: > > - DataSourceResolver: A new pluggable interface for routing JDBC > connections based on RealmContext and StoreType. > - Modular Design: Decoupled the resolution implementation into the > runtime-common module. > - Consistency: Utilizes a type-safe StoreType enum and aligns with > existing RealmContext patterns. > > The PR has been refined with feedback from @dimas-b and is now ready for > community review. I'd appreciate any feedback on the overall approach. > > Best regards, > > Subham Sangwan > GitHub: Subham-KRLX > > [1] https://github.com/apache/polaris/pull/3960 > [2] https://github.com/apache/polaris/issues/3890 >
