[
https://issues.apache.org/jira/browse/AMBARI-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568252#comment-14568252
]
Sumit Mohanty commented on AMBARI-11601:
----------------------------------------
Apparently, the HBase scripts in the stack definition also create this folder.
I think this variable was there some time back and got removed from default
hbase-site. That might explain why scripts have the logic to create the folder
in HDFS.
+1.
> Point hbase.bulkload.staging.dir to accessible directory for unsecure
> deployment
> --------------------------------------------------------------------------------
>
> Key: AMBARI-11601
> URL: https://issues.apache.org/jira/browse/AMBARI-11601
> Project: Ambari
> Issue Type: Improvement
> Reporter: Ted Yu
> Attachments: ambari-11601-v1.patch
>
>
> Since SecureBulkLoadEndpoint is loaded in unsecure hbase deployment, we need
> an accessible directory for hbase.bulkload.staging.dir
> By default, hbase.bulkload.staging.dir points to
> /user/$\{user.name\}/hbase-staging
> However, if /user/$\{user.name\} doesn't exist on hdfs, region server would
> abort when SecureBulkLoadEndpoint is started.
> This issue points hbase.bulkload.staging.dir to an accessible directory
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
