hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yongzhi Chen (JIRA)" <>
Subject [jira] [Commented] (HIVE-11150) Remove wrong warning message related to chgrp
Date Wed, 01 Jul 2015 12:56:04 GMT


Yongzhi Chen commented on HIVE-11150:

[~Yibing], I tried to change 20Shims and 20SShims in our system, for we are not building hadoop-1
any longer, so I decided not put into upstream for lack of testing and some risk (for the
code a little different).
For chmod, I think we need not make change for it used for permissions, and permissions should
always have values:

   * Get FsPermission associated with the file.
   * @return permssion. If a filesystem does not have a notion of permissions
   *         or if permissions could not be determined, then default 
   *         permissions equivalent of "rwxrwxrwx" is returned.
  public FsPermission getPermission() {
    return permission;

> Remove wrong warning message related to chgrp
> ---------------------------------------------
>                 Key: HIVE-11150
>                 URL:
>             Project: Hive
>          Issue Type: Bug
>          Components: Shims
>    Affects Versions: 0.13.0, 0.14.0, 1.0.0, 1.2.0
>            Reporter: Yongzhi Chen
>            Assignee: Yongzhi Chen
>            Priority: Minor
>         Attachments: HIVE-11150.1.patch
> When using other file system other than hdfs, users see warning message regarding hdfs
chgrp. The warning is very annoying and confusing. We'd better remove it. 
> The warning example:
> {noformat}
> hive> insert overwrite table s3_test select total_emp, salary, description from sample_07
limit 5;
> -chgrp: '' does not match expected pattern for group
> Usage: hadoop fs [generic options] -chgrp [-R] GROUP PATH...
> Total jobs = 1
> Launching Job 1 out of 1
> Number of reduce tasks determined at compile time: 1
> In order to change the average load for a reducer (in bytes):
>   set hive.exec.reducers.bytes.per.reducer=<number>
> {noformat}

This message was sent by Atlassian JIRA

View raw message