[
https://issues.apache.org/jira/browse/LENS-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jaideep Dhok updated LENS-349:
------------------------------
Comment: was deleted
(was: Proposing design -
# Keep track of lens session to current database in HiveDriver
# Add new method in HiveDriver to check if current lens database is different
from the one known to Hive driver for that session.
# If DB is different, remove jars of old DB from Hive session
# Jars of new DB will be added by QueryExecutionServiceImpl according to
current logic.
{code}
// New method will be called by QueryExecutionServiceImpl instead of
areRsourcesAddedForSession
public boolean refreshSessionDBResources(String sessionHandle, String
currentDb) {
if (!currentDb.equals(sessionToDbMap.get(sessionHandle))) {
removeDbResouces(sessionHandle);
sessionToDbMap.put(sessionHandle, currentDb);
return true;
}
return areRsourcesAddedForSession(sessionHandle);
}
// New method in LensSessionService, will be used by HiveDriver to get
resources to remove for the old DB.
public Map<String, List<String>> getDBResources()
{code}
)
> Hive driver jars should get refreshed with db switches
> ------------------------------------------------------
>
> Key: LENS-349
> URL: https://issues.apache.org/jira/browse/LENS-349
> Project: Apache Lens
> Issue Type: Sub-task
> Components: driver-hive, server
> Reporter: Jaideep Dhok
> Assignee: Jaideep Dhok
>
> DB switch should take care of updating DB jars in the Hive session.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
