[ 
https://issues.apache.org/jira/browse/HADOOP-14488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sean Mackrory updated HADOOP-14488:
-----------------------------------
    Attachment: HADOOP-14488-HADOOP-13345-003.patch

Yeah something like that. The next iteration of HADOOP-14457 made it not 
conflict with this anymore, so just posting a patch that shouldn't conflict. 
I'm afraid I'm going to be out of the office the rest of today, so I'll pick 
this up on Monday with a test case of the fully-recursive listing and that 
change. Not sure if we want to commit this in the mean time to fix all existing 
test cases or if people are good to wait until it's correct for fully-recursive 
listings too. I'm good either way. 

> s3guard listStatus fails after renaming file into directory
> -----------------------------------------------------------
>
>                 Key: HADOOP-14488
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14488
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Steve Loughran
>            Priority: Blocker
>         Attachments: HADOOP-14488-HADOOP-13345-001.patch, 
> HADOOP-14488-HADOOP-13345-002.patch, HADOOP-14488-HADOOP-13345-003.patch, 
> output.txt
>
>
> Running scala integration test with inconsistent s3 client & local DDB enabled
> {code}
> fs.rename("work/task-00/part-00", work)
> fs.listStatus(work)
> {code}
> The list status work fails with a message about the childStatus not being a 
> child of the parent. 
> Hypothesis: rename isn't updating the child path entry



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to