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
