Yeah, it wouldn't matter if incorrect config was in hive-site.xml. But I can foresee an admin seeing mysql connection info in hive-site.xml and wondering why the heck hive isn't starting. I think it'd be nice to clear those out so it's obvious that we have no mysql user/password in the hive config.
For the other thing, hive creates tables on the db given to it by mysql. If the mysql relation is removed (which an admin might do if they want to swap it out for mariadb), the mysql unit would still have the hive database configured. Now fast forward 2 years and the mysql admin being like "oh crap, what are all these databases doing here?". I think anybody that creates a database on a db unit should be responsible for removing that db if that relation is removed. This is all nice-to-have. No functionality is breaking, but I wanted to file the bug so I don't forget. -- You received this bug notification because you are a member of Juju Big Data Development, which is a bug assignee. https://bugs.launchpad.net/bugs/1490643 Title: remove db on db-relation-departed Status in apache-hive package in Juju Charms Collection: New Bug description: Hive should remove its database from the db unit when the relevant realtion-departed (or -broken) hook fires. This means creating the right hook to do the removal and potentially adding logic to clean old connection info from hive-site.xml. To manage notifications about this bug go to: https://bugs.launchpad.net/charms/+source/apache-hive/+bug/1490643/+subscriptions -- Mailing list: https://launchpad.net/~bigdata-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~bigdata-dev More help : https://help.launchpad.net/ListHelp
