The configuration for a primary metastore has became increasingly similar to the configuration for a federated metastore over time, to the point where there are duplications in the documentation for the options to configure a metastore. It would reduce confusion to have only one type of metastore and discard the distinction between "primary" and "federated".
Crucially this needs to be done in a way that ensures that the differences in configuration for a "primary" database can still be applied.Currently, there are few exceptions in duplications:
database-prefix (ignored for primary metastore)access-control-type (fewer options for federated metastore)mapped-databases (not an option for primary metastore)
These will need to be available across both types before they can be combined.
The configuration for a primary metastore has became increasingly similar to the configuration for a federated metastore over time, to the point where there are duplications in the documentation for the options to configure a metastore. It would reduce confusion to have only one type of metastore and discard the distinction between "primary" and "federated".
Crucially this needs to be done in a way that ensures that the differences in configuration for a "primary" database can still be applied.Currently, there are few exceptions in duplications:
database-prefix(ignored for primary metastore)access-control-type(fewer options for federated metastore)mapped-databases(not an option for primary metastore)These will need to be available across both types before they can be combined.