Currently, Kylo stores feed results in Hive tables where the database name is determined by the category assigned to the feed. This includes target tables as well as work tables.
A customer would like to have the ability to more precisely control the placement of tables in Hive. Specifically, they would like to be able override the default database name in Hive with another existing Hive database for target tables. They would also like the capability to designate a separate existing Hive database for work tables.
From a business perspective, this will allow the customer to publish target tables separately from work tables with a separate level of security, and it would allow feeds to place tables in already existing databases or applications without the need for databases to have a one to one correspondence to Kylo categories.