[ 
https://issues.apache.org/jira/browse/HDFS-13453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16443466#comment-16443466
 ] 

Dibyendu Karmakar commented on HDFS-13453:
------------------------------------------

Thanks [~elgoiri].

Using this above mentioned approach, when mount table will have */parent* as 
well as */parent/child* mount point it will return the modified date of 
*/parent/child* for */parent*. But the actual modified date of /parent will be 
different in mount table entry. I think if we have /parent in mount table we 
should return the actual modified date present in the mount table. When /parent 
will not be there in mount table, in that case we will return modified date of 
/parent/child.

What do you suggest?

> RBF: getMountPointDates should fetch latest subdir time/date when parent dir 
> is not present but /parent/child dirs are present in mount table
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-13453
>                 URL: https://issues.apache.org/jira/browse/HDFS-13453
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Dibyendu Karmakar
>            Assignee: Dibyendu Karmakar
>            Priority: Major
>         Attachments: HDFS-13453-000.patch, HDFS-13453-001.patch
>
>
> [HDFS-13386|https://issues.apache.org/jira/browse/HDFS-13386] is not handling 
> the case when /parent in not present in mount table but /parent/subdir is in 
> mount table.
> In this case getMountPointDates is not able to fetch the latest time for 
> /parent as /parent is not present in mount table.
> For this scenario we will display latest modified subdir date/time as /parent 
> modified time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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

Reply via email to