You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "John (JIRA)" <ji...@apache.org> on 2014/06/09 16:38:01 UTC
[jira] [Commented] (SQOOP-1246) HBaseImportJob should add job
authtoken only if HBase is secured
[ https://issues.apache.org/jira/browse/SQOOP-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14025224#comment-14025224 ]
John commented on SQOOP-1246:
-----------------------------
SEE ALSO https://issues.apache.org/jira/browse/SQOOP-599.
> HBaseImportJob should add job authtoken only if HBase is secured
> ----------------------------------------------------------------
>
> Key: SQOOP-1246
> URL: https://issues.apache.org/jira/browse/SQOOP-1246
> Project: Sqoop
> Issue Type: Bug
> Components: hbase-integration
> Affects Versions: 1.4.4
> Reporter: Aditya Kishore
> Assignee: Aditya Kishore
> Fix For: 1.4.5
>
> Attachments: SQOOP-1246.patch, SQOOP-1246_v2.patch
>
>
> Sqoop's HBase import job incorrectly checks if Hadoop is secured instead of HBase is secured before deciding to add an HBase authtoken,
> {code:title=HBaseImportJob.java}
> @Override
> /** Create the target HBase table before running the job. */
> protected void jobSetup(Job job) throws IOException, ImportException {
> ...
> // Get method isSecurityEnabled
> Method isSecurityEnabled = User.class.getMethod("isSecurityEnabled");
> ...
> // Obtain security token if needed
> if ((Boolean)isSecurityEnabled.invoke(null)) {
> obtainAuthTokenForJob.invoke(user, conf, job);
> }
> {code}
> which of course fails if Hadoop is secured but HBase is not.
--
This message was sent by Atlassian JIRA
(v6.2#6252)