[ 
https://issues.apache.org/jira/browse/BIGTOP-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13534153#comment-13534153
 ] 

Mark Grover commented on BIGTOP-811:
------------------------------------

The intent and idea is great. Thanks, Sean!
A couple things:
1. May I propose that we provide a configuration property that can be used to 
override the location (unless we already do so) of mysql-connector-java.
2. Should we call it mysql-connector-java or keep the generic like 
sql-connector-java so the same idea can apply to other sql connectors that 
aren't shipped with the distribution.
3. Can you think of a scenario where different components would want to use 
different versions of connectors (arguably connecting to different databases)? 
As a good engineering practice, I'd expect users to use the same relational 
database for say sqoop and hive metastores but if they have a separate 
metastore for sqoop and separate metastore for hive and their versions 
mismatch, they would need separate connectors for these. If you consider this 
to be a reasonable use case, we obviously can't help them here so let's make 
sure we don't make their life more difficult either.
Thoughts?
                
> Auto-detect MySQL-Java connector
> --------------------------------
>
>                 Key: BIGTOP-811
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-811
>             Project: Bigtop
>          Issue Type: New Feature
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>
> For components that require the installation of additional artifacts that 
> Bigtop cannot distribute (due to license incompatability or other issues), 
> Bigtop should provide both a standardized location to which the artifacts can 
> be installed, and the ability to auto-detect the locations to which they may 
> already be installed.
> Specifically, Sqoop and Hive (and possibly other components) require the 
> installation of the MySQL-Java connector when using MySQL for imports, 
> exports, or metadata storage. This needs to be done by copying the JAR to a 
> directory that is already in the classpath for those components (such as 
> /usr/lib/sqoop/lib and /usr/lib/hive/lib). Some repositories distribute 
> packages that install the jar to /usr/share/java.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to