You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Enis Soztutar (JIRA)" <ji...@apache.org> on 2013/02/27 05:24:13 UTC

[jira] [Resolved] (HBASE-7917) Documentation for secure bulk load

     [ https://issues.apache.org/jira/browse/HBASE-7917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Enis Soztutar resolved HBASE-7917.
----------------------------------

      Resolution: Fixed
    Hadoop Flags: Reviewed

Committed this. Thanks Stack, Francis. 
                
> Documentation for secure bulk load
> ----------------------------------
>
>                 Key: HBASE-7917
>                 URL: https://issues.apache.org/jira/browse/HBASE-7917
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Enis Soztutar
>            Assignee: Enis Soztutar
>             Fix For: 0.95.0, 0.98.0
>
>         Attachments: hbase-7917_v1.patch, hbase-7917_v2.patch
>
>
> One of our tests for bulk loading on a secure cluster failed, because of it was 
> not configured properly. We should document the setup. 
> From SecureBulkLoadEndpoint: 
> {code}
> 1. Create an hbase owned staging directory which is
>  * world traversable (711): /hbase/staging
>  * 2. A user writes out data to his secure output directory: /user/foo/data
>  * 3. A call is made to hbase to create a secret staging directory
>  * which globally rwx (777): /user/staging/averylongandrandomdirectoryname
>  * 4. The user makes the data world readable and writable, then moves it
>  * into the random staging directory, then calls bulkLoadHFiles()
>  *
>  * Like delegation tokens the strength of the security lies in the length
>  * and randomness of the secret directory.
> {code}
> See HBASE-5498 for details on secure bulk load. 

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