sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Jarcec Cecho (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-501) Infrastructure to support input of sensitive information like passwords in the client shell
Date Fri, 05 Oct 2012 15:48:03 GMT

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

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

I'm not expecting that Oozie will need to read from stdin in sqoop 2 case. We've refactored
entire architecture by for example introducing server-client model, where server is holding
all job metadata. I'm expecting that administrator will use sqoop ui to create job metadata
outside of oozie and Oozie will just "execute" those stored job metadata (possibly multiple
times) using REST interface. Thus there shouldn't be any need for oozie to read data from
stdin. 


Jarcec
                
> Infrastructure to support input of sensitive information like passwords in the client
shell
> -------------------------------------------------------------------------------------------
>
>                 Key: SQOOP-501
>                 URL: https://issues.apache.org/jira/browse/SQOOP-501
>             Project: Sqoop
>          Issue Type: Task
>            Reporter: Arvind Prabhakar
>            Assignee: Vasanth kumar RJ
>             Fix For: 2.0.0
>
>
> For example, a password should be entered in a manner that keeps it secure through the
input and the remaining session.

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

Mime
View raw message