[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid
[
https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer updated HDFS-4325:
---
Labels: BB2015-05-TBR (was: )
ClientProtocol.createSymlink parameter dirPerm invalid
--
Key: HDFS-4325
URL: https://issues.apache.org/jira/browse/HDFS-4325
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs-client, namenode
Affects Versions: 2.0.4-alpha
Reporter: Binglin Chang
Assignee: Binglin Chang
Labels: BB2015-05-TBR
Attachments: HDFS-4325.v1.patch
{code}
* @param link The path of the link being created.
* @param dirPerm permissions to use when creating parent directories
* @param createParent - if true then missing parent dirs are created
* if false then parent must exist
{code}
According to javadoc, auto created parent dir's permissions will be dirPerm,
but in fact directory permissions are always inherit from parent directory
plus u+wx.
IMHO, createSymlink behavior should be the same as create, which also inherit
parent dir permission, so the current behavior makes sense, but the related
dirPerm parameters should be removed cause it is invalid and confusing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid
[
https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Binglin Chang updated HDFS-4325:
Target Version/s: 2.1.0-beta (was: 2.0.3-alpha)
Affects Version/s: (was: 2.0.2-alpha)
2.0.4-alpha
Assignee: Binglin Chang
ClientProtocol.createSymlink parameter dirPerm invalid
--
Key: HDFS-4325
URL: https://issues.apache.org/jira/browse/HDFS-4325
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs-client, namenode
Affects Versions: 2.0.4-alpha
Reporter: Binglin Chang
Assignee: Binglin Chang
{code}
* @param link The path of the link being created.
* @param dirPerm permissions to use when creating parent directories
* @param createParent - if true then missing parent dirs are created
* if false then parent must exist
{code}
According to javadoc, auto created parent dir's permissions will be dirPerm,
but in fact directory permissions are always inherit from parent directory
plus u+wx.
IMHO, createSymlink behavior should be the same as create, which also inherit
parent dir permission, so the current behavior makes sense, but the related
dirPerm parameters should be removed cause it is invalid and confusing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid
[
https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Binglin Chang updated HDFS-4325:
Status: Patch Available (was: Open)
ClientProtocol.createSymlink parameter dirPerm invalid
--
Key: HDFS-4325
URL: https://issues.apache.org/jira/browse/HDFS-4325
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs-client, namenode
Affects Versions: 2.0.4-alpha
Reporter: Binglin Chang
Assignee: Binglin Chang
{code}
* @param link The path of the link being created.
* @param dirPerm permissions to use when creating parent directories
* @param createParent - if true then missing parent dirs are created
* if false then parent must exist
{code}
According to javadoc, auto created parent dir's permissions will be dirPerm,
but in fact directory permissions are always inherit from parent directory
plus u+wx.
IMHO, createSymlink behavior should be the same as create, which also inherit
parent dir permission, so the current behavior makes sense, but the related
dirPerm parameters should be removed cause it is invalid and confusing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid
[
https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Binglin Chang updated HDFS-4325:
Attachment: HDFS-4325.v1.patch
Because ClientProtocol is in RPC and param dirPerm is defined as required in
proto files, I am not sure whether or not to remove it, so I just add some
comments to clarify this parameter is invalid, and do some minor modification
in server side.
ClientProtocol.createSymlink parameter dirPerm invalid
--
Key: HDFS-4325
URL: https://issues.apache.org/jira/browse/HDFS-4325
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs-client, namenode
Affects Versions: 2.0.4-alpha
Reporter: Binglin Chang
Assignee: Binglin Chang
Attachments: HDFS-4325.v1.patch
{code}
* @param link The path of the link being created.
* @param dirPerm permissions to use when creating parent directories
* @param createParent - if true then missing parent dirs are created
* if false then parent must exist
{code}
According to javadoc, auto created parent dir's permissions will be dirPerm,
but in fact directory permissions are always inherit from parent directory
plus u+wx.
IMHO, createSymlink behavior should be the same as create, which also inherit
parent dir permission, so the current behavior makes sense, but the related
dirPerm parameters should be removed cause it is invalid and confusing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid
[
https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Binglin Chang updated HDFS-4325:
Affects Version/s: (was: 2.0.3-alpha)
(was: 3.0.0)
2.0.2-alpha
ClientProtocol.createSymlink parameter dirPerm invalid
--
Key: HDFS-4325
URL: https://issues.apache.org/jira/browse/HDFS-4325
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs-client, namenode
Affects Versions: 2.0.2-alpha
Reporter: Binglin Chang
{code}
* @param link The path of the link being created.
* @param dirPerm permissions to use when creating parent directories
* @param createParent - if true then missing parent dirs are created
* if false then parent must exist
{code}
According to javadoc, auto created parent dir's permissions will be dirPerm,
but in fact directory permissions are always inherit from parent directory
plus u+wx.
IMHO, createSymlink behavior should be the same as create, which also inherit
parent dir permission, so the current behavior makes sense, but the related
dirPerm parameters should be removed cause it is invalid and confusing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid
[
https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Binglin Chang updated HDFS-4325:
Target Version/s: 2.0.3-alpha
Fix Version/s: (was: 2.0.3-alpha)
ClientProtocol.createSymlink parameter dirPerm invalid
--
Key: HDFS-4325
URL: https://issues.apache.org/jira/browse/HDFS-4325
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs-client, namenode
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Binglin Chang
{code}
* @param link The path of the link being created.
* @param dirPerm permissions to use when creating parent directories
* @param createParent - if true then missing parent dirs are created
* if false then parent must exist
{code}
According to javadoc, auto created parent dir's permissions will be dirPerm,
but in fact directory permissions are always inherit from parent directory
plus u+wx.
IMHO, createSymlink behavior should be the same as create, which also inherit
parent dir permission, so the current behavior makes sense, but the related
dirPerm parameters should be removed cause it is invalid and confusing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HDFS-4325) ClientProtocol.createSymlink parameter dirPerm invalid
[
https://issues.apache.org/jira/browse/HDFS-4325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Binglin Chang updated HDFS-4325:
Component/s: namenode
hdfs-client
Affects Version/s: 2.0.3-alpha
3.0.0
Fix Version/s: 2.0.3-alpha
ClientProtocol.createSymlink parameter dirPerm invalid
--
Key: HDFS-4325
URL: https://issues.apache.org/jira/browse/HDFS-4325
Project: Hadoop HDFS
Issue Type: Bug
Components: hdfs-client, namenode
Affects Versions: 3.0.0, 2.0.3-alpha
Reporter: Binglin Chang
Fix For: 2.0.3-alpha
{code}
* @param link The path of the link being created.
* @param dirPerm permissions to use when creating parent directories
* @param createParent - if true then missing parent dirs are created
* if false then parent must exist
{code}
According to javadoc, auto created parent dir's permissions will be dirPerm,
but in fact directory permissions are always inherit from parent directory
plus u+wx.
IMHO, createSymlink behavior should be the same as create, which also inherit
parent dir permission, so the current behavior makes sense, but the related
dirPerm parameters should be removed cause it is invalid and confusing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
