[jira] [Updated] (HDFS-5767) NFS implementation assumes userName userId mapping to be unique, which is not true sometimes

[ https://issues.apache.org/jira/browse/HDFS-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Li updated HDFS-5767: - Fix Version/s: 2.4.0 > NFS implementation assumes userName userId mapping to be unique, which is not > tr

[jira] [Updated] (HDFS-5767) NFS implementation assumes userName userId mapping to be unique, which is not true sometimes

[ https://issues.apache.org/jira/browse/HDFS-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Li updated HDFS-5767: - Resolution: Fixed Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) > NFS im

[jira] [Updated] (HDFS-5767) NFS implementation assumes userName userId mapping to be unique, which is not true sometimes

[ https://issues.apache.org/jira/browse/HDFS-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Li updated HDFS-5767: - Summary: NFS implementation assumes userName userId mapping to be unique, which is not true sometimes (wa

[jira] [Updated] (HDFS-5767) Nfs implementation assumes userName userId mapping to be unique, which is not true sometimes

[ https://issues.apache.org/jira/browse/HDFS-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated HDFS-5767: Attachment: HDFS-5767.003.patch > Nfs implementation assumes userName userId mapping to be unique, w

[jira] [Updated] (HDFS-5767) Nfs implementation assumes userName userId mapping to be unique, which is not true sometimes

[ https://issues.apache.org/jira/browse/HDFS-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated HDFS-5767: Attachment: HDFS-5767.002.patch > Nfs implementation assumes userName userId mapping to be unique, w

[jira] [Updated] (HDFS-5767) Nfs implementation assumes userName userId mapping to be unique, which is not true sometimes

[ https://issues.apache.org/jira/browse/HDFS-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated HDFS-5767: Status: Patch Available (was: Reopened) This patch takes first (name, id) entry as the valid one. I

[jira] [Updated] (HDFS-5767) Nfs implementation assumes userName userId mapping to be unique, which is not true sometimes

[ https://issues.apache.org/jira/browse/HDFS-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated HDFS-5767: Attachment: HDFS-5767.001.patch > Nfs implementation assumes userName userId mapping to be unique, w

[jira] [Updated] (HDFS-5767) Nfs implementation assumes userName userId mapping to be unique, which is not true sometimes

[ https://issues.apache.org/jira/browse/HDFS-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brandon Li updated HDFS-5767: - Priority: Blocker (was: Major) > Nfs implementation assumes userName userId mapping to be unique, which i

[jira] [Updated] (HDFS-5767) Nfs implementation assumes userName userId mapping to be unique, which is not true sometimes

[ https://issues.apache.org/jira/browse/HDFS-5767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yongjun Zhang updated HDFS-5767: Description: I'm seeing that the nfs implementation assumes unique pair to be returned by command