caican00 opened a new issue, #5574:
URL: https://github.com/apache/gravitino/issues/5574
### Describe the feature
In our real-world scenario, a generic iceberg catalog name such as
`iceberg_{cluster_name}` is used in a region, regardless of the specific
iceberg backend metastore.
Users do not need to care about the underlying metadata storage service.
When we do the migration of the metadata service at the bottom of iceberg,
users should not be aware of it, and they should not be asked to modify the
iceberg catalog name in their sql, otherwise it will be very difficult to
implement.
Therefore, we want to implicitly implement the switching of iceberg's
underlying metadata storage service without requiring users to modify their sql
in iceberg rest server.
My initial thought is:
supporting a `master-slave` backend catalog in the iceberg rest server，as
shown in the figure.
1. For new tables, access master metastore directly to create, read, or
modify metadata
2. For the old table, if it exists in master metastore, the metadata is read
or modified directly based on master metastore.
If it does not exist in master metastore, copy the metadata from slave
metastore to master metastore at first, and then read or modify the metadata
based on master metastore.
### Motivation
_No response_
### Describe the solution
_No response_
### Additional context
_No response_
--
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]
