Hi All, This discussion stems [1] from PR [5328], but it is rooted in more fundamental Polaris behaviours.
ATM the codebase uses a combination of StorageAccessConfig and _default_ table properties for constructing server-side FileIO objects. Note that it already deviates from what clients may use. Load table responses advertise FileIO-related properties in the REST API-level config section. These properties include vended credentials and endpoints. Generally, IRC config properties are sufficient for clients to construct operational FileIO objects to access storage files for tables loaded via Polaris. Therefore, I propose that Polaris code use only StorageAccessConfig for constructing server-side FileIO objects. Thoughts? [1] https://github.com/apache/polaris/pull/5328#discussion_r4184400135 [5328] https://github.com/apache/polaris/pull/5328 Cheers, Dmitri.
