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

Jarek Jarcec Cecho commented on SQOOP-1152:
-------------------------------------------

Hi [~iwasakims],
thank you very much for improving this! We've used {{common.loader}} instead of 
{{shared.loader}} to remain compatible with downstream project called BigTop 
that is doing this not only for Sqoop server, but also for example for Oozie. 
So it would be great to remain consistent!

I like the iteration of all possible directories for Hadoop 2, but I'm afraid 
that users of Hadoop 1 might get confused. What about putting multiple 
{{common.loader}} entries there that will be commented out, but prepared for 
particular Hadoop version? Something like:

{code}
# <<General introduction how the common.loader should be used and what needs to 
be specified here>>
#
# Example for Hadoop 1.x
#common.loader=...
#
# Example for Hadoop 2.x
common.loader=...
{code}
                
> The classpath settings in catalina.properties is not straightforward
> --------------------------------------------------------------------
>
>                 Key: SQOOP-1152
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1152
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: sqoop2-dist
>    Affects Versions: 2.0.0
>            Reporter: Masatake Iwasaki
>            Priority: Trivial
>         Attachments: SQOOP-1152-0.patch
>
>
> The classpath settings in catalina.properties which works for hadoop200 is 
> not straightforward. It is preferable to hava more kind default settings, at 
> least in commented out form.
> Note: I tried variable substitution in catalina.properties but it seems not 
> to be available on Tomcat6. 
> https://issues.apache.org/bugzilla/show_bug.cgi?id=50677

--
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