[
https://issues.apache.org/jira/browse/AMBARI-19328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15788174#comment-15788174
]
Hadoop QA commented on AMBARI-19328:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12845187/AMBARI-19328.patch
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 2 new
or modified test files.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-server.
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/9870//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/9870//console
This message is automatically generated.
> Fix permissions for Druid config files and segmentCache directory
> -----------------------------------------------------------------
>
> Key: AMBARI-19328
> URL: https://issues.apache.org/jira/browse/AMBARI-19328
> Project: Ambari
> Issue Type: Bug
> Reporter: Nishant Bangarwa
> Assignee: Nishant Bangarwa
> Fix For: trunk, 2.5.0
>
> Attachments: AMBARI-19328.patch
>
>
> 1) Druid config files contain metadata store password - make sure they are
> accessible only to druid user.
> 2) On historical nodes druid segment cache locations contain druid segments
> which may have sensitive data, they also need to be accesible by only druid
> user.
> 3) Druid middlemanagers use baseTaskDir to store intermediate segments, they
> also need to be secured.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
