You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, users need to upload catalog resources like hive-site.xml and keytabs, which would be stored in the AMS home and the database. However, it's cumbersome to maintain 30+ catalogs manually like this. Moreover, it adds to the initiation time of AMS cause a standby/new AMS has to write the resources to the local folders.
We should support externalized resources. For example. AMS catalogs store the hive conf path instead of the content of hive-site.xml. Users using externalized should ensure each AMS instance has access to the resources.
Description
Currently, users need to upload catalog resources like hive-site.xml and keytabs, which would be stored in the AMS home and the database. However, it's cumbersome to maintain 30+ catalogs manually like this. Moreover, it adds to the initiation time of AMS cause a standby/new AMS has to write the resources to the local folders.
We should support externalized resources. For example. AMS catalogs store the hive conf path instead of the content of hive-site.xml. Users using externalized should ensure each AMS instance has access to the resources.
Use case/motivation
No response
Describe the solution
No response
Subtasks
No response
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: