hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (Jira)" <>
Subject [jira] [Commented] (HIVE-22599) Query results cache: 733 permissions check is not necessary
Date Wed, 11 Dec 2019 00:08:00 GMT


Hive QA commented on HIVE-22599:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 17762 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12988465 - PreCommit-HIVE-Build

> Query results cache: 733 permissions check is not necessary
> -----------------------------------------------------------
>                 Key: HIVE-22599
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Jason Dere
>            Assignee: Jason Dere
>            Priority: Major
>         Attachments: HIVE-22599.1.patch
> The query results cache initialization makes a call to Utilties.ensurePathIsWritable(),
which checks the results cache directory for 733 permissions (default cache dir is
> {{/tmp/hive/_resultscache_).}}
> The 733 permissions (at least the 033 part) are not actually necessary - we actually
don't really want the results cache directory to be world-writable, and the subdirectories
we create within this one are actually done with 700 perms. So I think the call to Utilties.ensurePathIsWritable()
can be removed.

This message was sent by Atlassian Jira

View raw message