blackfaced commented on issue #7953: URL: https://github.com/apache/gravitino/issues/7953#issuecomment-3241976513
> This is a general problem not limited to Hive metastore uri and Spark, How to handle the Gravitino catalog properties in different networks(or region)? Propose adding `gravitino.region.$regionName.$propertyName` properties to represent region variables which take effect in the specific region. Take `metastore.uri` for example, we could define `gravitino.region.north.metastore.uri` in catalog properties, in Gravitino client side, we could extract the corresponding `metastore.uri` according to the `gravitino.region.name` configuration or `GRAVITINO_REGION_NAME` environment variables, if there are no region variables, the client will use the default `metastore.uri`, [@jerryshao](https://github.com/jerryshao) [@blackfaced](https://github.com/blackfaced) WDYT? @FANNG1 Thanks for raising this proposal. In typical cloud scenarios, each region usually deploys its own service instance, and the same applies to compute engines. Therefore, from the engine’s perspective, it doesn’t need to be aware of which specific region it’s operating in, but rather whether it should use an internal (private) address, a region-wide address, or a public address. Region-specific configuration might be useful in multi-region setups, but currently, we haven’t seen strong demand for this feature. It could be considered in the future if more use cases arise. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
