[
https://issues.apache.org/jira/browse/LENS-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15171834#comment-15171834
]
Badrinath Kulkarni commented on LENS-317:
-----------------------------------------
Updated approach :
Support both old and new flows. Over a period of time, we can move to new flow
completely.
Existing structure ->
{noformat}
/base_folder
/DB_A
-jar_order
-hive-metastore-0.13.3-inm.jar
-lens-ship-jars-2.5.3-inm.jar
-db_a_specific_1.jar
-db_a_specific_2.jar
/DB_B
-jar_order
-hive-metastore-0.13.3-inm.jar
-lens-ship-jars-2.5.3-inm.jar
-db_b_specific_1.jar
-db_b_specific_2.jar
{noformat}
At present, there is a "jar_order" file in each DB folder. So, if "jar_order"
file is present in a particular DB folder, then those jars will be loaded. This
is the existing flow.
How old flow will be supported :
Now,if user tries to upload a jar into a particular DB folder using "Add DB
Jar" API and "jar_order" file is present in that DB folder, then an exception
will be thrown with a proper message.
If no "jar_file" is present in a particular DB folder and when user uploads a
jar file, that new jar file will be used by new job as explained below -
Updated new flow ->
{noformat}
/base_folder
-lens-ship.jar
/DB_A
-db_a_version_1.jar
-db_a_version_2.jar
-db_a_version_3.jar
/DB_B
-db_b_version_1.jar
-db_b_version_2.jar
-db_b_version_3.jar
{noformat}
1. All the common jars will be consolidated into one single jar (lens-ship.jar)
2. Jars corresponding to a particular DB will have a counter in their name to
help identify the latest jar.
> Server side calls for updating database jars
> --------------------------------------------
>
> Key: LENS-317
> URL: https://issues.apache.org/jira/browse/LENS-317
> Project: Apache Lens
> Issue Type: Improvement
> Components: cube, server
> Reporter: Jaideep Dhok
> Assignee: Badrinath Kulkarni
> Fix For: 2.6
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
