Hi Dmitri and Adnan, I have created a new pull request ( https://github.com/apache/polaris/pull/4023) that I think better aligns with the community consensus. Please let me know your thoughts; I am also open to removing any tests that may be considered extraneous.
Currently, the override behavior updates the storageName while preserving the inherited storage type. This allows an AWS catalog to be overridden by a different AWS-named credential, but it does not yet support switching to Azure or GCS at the namespace or table scope via polaris.storage.name alone. My planned follow-up items include: - Adding explicit leaf-scope cross-type override support (e.g., type + name semantics). - Extending validation and conflict handling for cross-type overrides. - Adding end-to-end vending tests for an AWS catalog overridden by Azure at the namespace scope and by GCS at the table scope. - Updating documentation to cover supported override combinations and migration behavior. Best regards, Srinivas Rishindra On Thu, Mar 12, 2026 at 4:11 PM Srinivas Rishindra <[email protected]> wrote: > Hi Dmitri, > > Thanks for following up on this. I apologize for the delayed response. I > have also unfortunately fallen behind on this work recently.. > > To answer your question about the review: please hold off on reviewing PR > #3923 any further for now. I am currently working on trimming it down. The > idea is to submit a much slimmer version first that strictly introduces the > inline StorageConfiguration so we can align on the core changes, and then > we can add more features incrementally. > > Regarding the implementation plan, I will put together a clear summary and > post it here by this weekend, along with the updated, lighter PR for the > first step. > > Thanks again for your patience and for the preliminary review comments > you've already shared. > > Best regards, > Srinivas Rishindra Pothireddi >
