You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Bikas Saha (Created) (JIRA)" <ji...@apache.org> on 2012/04/05 21:02:26 UTC
[jira] [Created] (HADOOP-8250) Investigate compatibility of symlink
usage
Investigate compatibility of symlink usage
------------------------------------------
Key: HADOOP-8250
URL: https://issues.apache.org/jira/browse/HADOOP-8250
Project: Hadoop Common
Issue Type: Sub-task
Components: native
Affects Versions: 1.1.0
Reporter: Bikas Saha
Assignee: Bikas Saha
Fix For: 1.1.0
The current Windows patch replaces symlink with copy. This jira tracks understanding the implications of this on expected functionality.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (HADOOP-8250) Investigate uses of FileUtil and
functional correctness based on current use cases
Posted by "Bikas Saha (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-8250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bikas Saha resolved HADOOP-8250.
--------------------------------
Resolution: Won't Fix
Multiple other jiras have superceded this.
> Investigate uses of FileUtil and functional correctness based on current use cases
> ----------------------------------------------------------------------------------
>
> Key: HADOOP-8250
> URL: https://issues.apache.org/jira/browse/HADOOP-8250
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: native
> Affects Versions: 1.1.0
> Reporter: Bikas Saha
> Assignee: Bikas Saha
>
> The current Windows patch replaces symlink with copy. This jira tracks understanding the implications of this change and others like it on expected functionality.
--
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