[
https://issues.apache.org/jira/browse/HADOOP-7018?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12932155#action_12932155
]
Doug Cutting commented on HADOOP-7018:
--------------------------------------
To be clearer:
- I understand that the relative path is useful and should be provided
- The relative path could be provided via a new class returned by FileContext
or could or a new method on the existing FileStatus.
- In either case, folks would need to update their code to use the new
functionality.
My question is: why should one approach be preferred over the other?
If we add a new class:
- we'd remove FileContext methods that return FileStatus
- add new methods that return FileStatusInfo
- any user programs that update to FileContext will also need to update all
their uses of FileStatus. A program could not easily update partially, e.g.,
still calling a library that accepts FileStatus but not FileStatusInfo.
If we add a new method:
- user programs could update incrementally
- user programs that adopt FileContext would not be compelled to update, so
programs may take longer to transition.
Does that sound right or have I mis-analyzed things? Are there other pros and
cons to the two approaches?
> FileContext's list operation should return local names in the status object
> rather then the full path.
> ------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-7018
> URL: https://issues.apache.org/jira/browse/HADOOP-7018
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Sanjay Radia
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
