Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consolidate primary and federated metastores into a single metastore type #154

Open
AnanaMJ opened this issue Feb 7, 2019 · 0 comments
Open

Comments

@AnanaMJ
Copy link
Contributor

AnanaMJ commented Feb 7, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant