Hi Subham, We discussed this PR in the Community Sync meeting today and I believe the main point the community would like to clarity was the use case(s) behind this change.
Would you be able to share any specific scenarios where multiple DataSources are necessary? If you do not have specific use cases in mind at this point, it's ok too. Please feel free to share your vision for this feature. Thanks, 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 >
