[
https://issues.apache.org/jira/browse/AMBARI-11601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568419#comment-14568419
]
Hudson commented on AMBARI-11601:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2780 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2780/])
AMBARI-11601. Point hbase.bulkload.staging.dir to accessible directory for
unsecure deployment (Ted Yu via srimanth) (sgunturi:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=7f75455fbac9e09d7d2fff5caaf94d38757d4474)
*
ambari-server/src/main/resources/stacks/HDP/2.2/services/HBASE/configuration/hbase-site.xml
> 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)
