[jira] [Updated] (HADOOP-8327) distcpv2 and distcpv1 jars should not coexist
[
https://issues.apache.org/jira/browse/HADOOP-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Joseph Evans updated HADOOP-8327:
Resolution: Fixed
Fix Version/s: 3.0.0
2.0.0
0.23.3
Status: Resolved (was: Patch Available)
Thanks Dave,
I have put this into trunk, branch-2, and branch-0.23
> distcpv2 and distcpv1 jars should not coexist
> -
>
> Key: HADOOP-8327
> URL: https://issues.apache.org/jira/browse/HADOOP-8327
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 0.23.2
>Reporter: Dave Thompson
>Assignee: Dave Thompson
> Fix For: 0.23.3, 2.0.0, 3.0.0
>
> Attachments: HADOOP-8327-branch-0.23.2.patch, HADOOP-8327.patch,
> HADOOP-8327.patch
>
>
> Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
> (hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
> hadoop-distcp-x.jar and hadoop-extras-x.jar end up in the same class path
> directory. This causes some undeterministic problems, where v1 is launched
> when v2 is intended, or even v2 is launched, but may later fail on various
> nodes because of mismatch with v1.
> According to
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
> ("Understanding class path wildcards")
> "The order in which the JAR files in a directory are enumerated in the
> expanded class path is not specified and may vary from platform to platform
> and even from moment to moment on the same machine."
> Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
> of distcpv1.
--
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] [Updated] (HADOOP-8327) distcpv2 and distcpv1 jars should not coexist
[
https://issues.apache.org/jira/browse/HADOOP-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson updated HADOOP-8327:
--
Attachment: HADOOP-8327.patch
Same trunk patch, just uploaded with grant license toggle flipped.
> distcpv2 and distcpv1 jars should not coexist
> -
>
> Key: HADOOP-8327
> URL: https://issues.apache.org/jira/browse/HADOOP-8327
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 0.23.2
>Reporter: Dave Thompson
>Assignee: Dave Thompson
> Attachments: HADOOP-8327-branch-0.23.2.patch, HADOOP-8327.patch,
> HADOOP-8327.patch
>
>
> Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
> (hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
> hadoop-distcp-x.jar and hadoop-extras-x.jar end up in the same class path
> directory. This causes some undeterministic problems, where v1 is launched
> when v2 is intended, or even v2 is launched, but may later fail on various
> nodes because of mismatch with v1.
> According to
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
> ("Understanding class path wildcards")
> "The order in which the JAR files in a directory are enumerated in the
> expanded class path is not specified and may vary from platform to platform
> and even from moment to moment on the same machine."
> Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
> of distcpv1.
--
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] [Updated] (HADOOP-8327) distcpv2 and distcpv1 jars should not coexist
[
https://issues.apache.org/jira/browse/HADOOP-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson updated HADOOP-8327:
--
Attachment: HADOOP-8327.patch
Though the intent is for the fix is branch 0.23.2, I'm attaching a trunk patch
now as it has been speculated that the auto patch is testing to trunk rather
than 0.23.2 as the attached patch name specifies.
> distcpv2 and distcpv1 jars should not coexist
> -
>
> Key: HADOOP-8327
> URL: https://issues.apache.org/jira/browse/HADOOP-8327
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 0.23.2
>Reporter: Dave Thompson
>Assignee: Dave Thompson
> Attachments: HADOOP-8327-branch-0.23.2.patch, HADOOP-8327.patch
>
>
> Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
> (hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
> hadoop-distcp-x.jar and hadoop-extras-x.jar end up in the same class path
> directory. This causes some undeterministic problems, where v1 is launched
> when v2 is intended, or even v2 is launched, but may later fail on various
> nodes because of mismatch with v1.
> According to
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
> ("Understanding class path wildcards")
> "The order in which the JAR files in a directory are enumerated in the
> expanded class path is not specified and may vary from platform to platform
> and even from moment to moment on the same machine."
> Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
> of distcpv1.
--
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] [Updated] (HADOOP-8327) distcpv2 and distcpv1 jars should not coexist
[
https://issues.apache.org/jira/browse/HADOOP-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson updated HADOOP-8327:
--
Tags: distcp distcpv1 distcpv2 classpath
Target Version/s: 0.23.3
Release Note: Resolve sporadic distcp issue due to having two DistCp
classes (v1 & v2) in the classpath.
Status: Patch Available (was: Open)
> distcpv2 and distcpv1 jars should not coexist
> -
>
> Key: HADOOP-8327
> URL: https://issues.apache.org/jira/browse/HADOOP-8327
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 0.23.2
>Reporter: Dave Thompson
>Assignee: Dave Thompson
> Attachments: HADOOP-8327-branch-0.23.2.patch
>
>
> Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
> (hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
> hadoop-distcp-x.jar and hadoop-extras-x.jar end up in the same class path
> directory. This causes some undeterministic problems, where v1 is launched
> when v2 is intended, or even v2 is launched, but may later fail on various
> nodes because of mismatch with v1.
> According to
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
> ("Understanding class path wildcards")
> "The order in which the JAR files in a directory are enumerated in the
> expanded class path is not specified and may vary from platform to platform
> and even from moment to moment on the same machine."
> Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
> of distcpv1.
--
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] [Updated] (HADOOP-8327) distcpv2 and distcpv1 jars should not coexist
[
https://issues.apache.org/jira/browse/HADOOP-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson updated HADOOP-8327:
--
Attachment: HADOOP-8327-branch-0.23.2.patch
The attached patch renames the v1 DistCp class to DistCpV1. Further, the
utility dependencies that use it Logalyzer and TestCopyFiles are adjusted to
use the renamed DistCpV1.
> distcpv2 and distcpv1 jars should not coexist
> -
>
> Key: HADOOP-8327
> URL: https://issues.apache.org/jira/browse/HADOOP-8327
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 0.23.2
>Reporter: Dave Thompson
>Assignee: Dave Thompson
> Attachments: HADOOP-8327-branch-0.23.2.patch
>
>
> Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
> (hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
> hadoop-distcp-x.jar and hadoop-extras-x.jar end up in the same class path
> directory. This causes some undeterministic problems, where v1 is launched
> when v2 is intended, or even v2 is launched, but may later fail on various
> nodes because of mismatch with v1.
> According to
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
> ("Understanding class path wildcards")
> "The order in which the JAR files in a directory are enumerated in the
> expanded class path is not specified and may vary from platform to platform
> and even from moment to moment on the same machine."
> Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
> of distcpv1.
--
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] [Updated] (HADOOP-8327) distcpv2 and distcpv1 jars should not coexist
[
https://issues.apache.org/jira/browse/HADOOP-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson updated HADOOP-8327:
--
Description:
Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
(hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
hadoop-distcp-x.jar and hadoop-extras-x.jar end up in the same class path
directory. This causes some undeterministic problems, where v1 is launched
when v2 is intended, or even v2 is launched, but may later fail on various
nodes because of mismatch with v1.
According to
http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
("Understanding class path wildcards")
"The order in which the JAR files in a directory are enumerated in the expanded
class path is not specified and may vary from platform to platform and even
from moment to moment on the same machine."
Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
of distcpv1.
was:
Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
(hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
hadoop-distcp-*.jar and hadoop-extras-*.jar end up in the same class path
directory. This causes some undeterministic problems, where v1 is launched
when v2 is intended, or even v2 is launched, but may later fail on various
nodes because of mismatch with v1.
According to
http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
("Understanding class path wildcards")
"The order in which the JAR files in a directory are enumerated in the expanded
class path is not specified and may vary from platform to platform and even
from moment to moment on the same machine."
Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
of distcpv1.
> distcpv2 and distcpv1 jars should not coexist
> -
>
> Key: HADOOP-8327
> URL: https://issues.apache.org/jira/browse/HADOOP-8327
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 0.23.2
>Reporter: Dave Thompson
>Assignee: Dave Thompson
>
> Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
> (hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
> hadoop-distcp-x.jar and hadoop-extras-x.jar end up in the same class path
> directory. This causes some undeterministic problems, where v1 is launched
> when v2 is intended, or even v2 is launched, but may later fail on various
> nodes because of mismatch with v1.
> According to
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
> ("Understanding class path wildcards")
> "The order in which the JAR files in a directory are enumerated in the
> expanded class path is not specified and may vary from platform to platform
> and even from moment to moment on the same machine."
> Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
> of distcpv1.
--
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] [Updated] (HADOOP-8327) distcpv2 and distcpv1 jars should not coexist
[
https://issues.apache.org/jira/browse/HADOOP-8327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Thompson updated HADOOP-8327:
--
Description:
Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
(hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
hadoop-distcp-*.jar and hadoop-extras-*.jar end up in the same class path
directory. This causes some undeterministic problems, where v1 is launched
when v2 is intended, or even v2 is launched, but may later fail on various
nodes because of mismatch with v1.
According to
http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
("Understanding class path wildcards")
"The order in which the JAR files in a directory are enumerated in the expanded
class path is not specified and may vary from platform to platform and even
from moment to moment on the same machine."
Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
of distcpv1.
was:
Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
(hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
hadoop-distcp-*.jar and hadoop-extras-*.jar end up in the same class path
directory. This causes some undeterministic problems, where v1 is launched
when v2 is intended, or even v2 is launched, but may later fail on various
nodes because of mismatch with v1.
According to
http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
("Understanding class path wildcards")
"The order in which the JAR files in a directory are enumerated in the expanded
class path is not specified and may vary from platform to platform and even
from moment to moment on the same machine."
Suggest distcpv1 be depricated at this point, possibly by discontinuing build
of distcpv1.
> distcpv2 and distcpv1 jars should not coexist
> -
>
> Key: HADOOP-8327
> URL: https://issues.apache.org/jira/browse/HADOOP-8327
> Project: Hadoop Common
> Issue Type: Bug
>Affects Versions: 0.23.2
>Reporter: Dave Thompson
>Assignee: Dave Thompson
>
> Distcp v2 (hadoop-tools/hadoop-distcp/...)and Distcp v1
> (hadoop-tools/hadoop-extras/...) are currently both built, and the resulting
> hadoop-distcp-*.jar and hadoop-extras-*.jar end up in the same class path
> directory. This causes some undeterministic problems, where v1 is launched
> when v2 is intended, or even v2 is launched, but may later fail on various
> nodes because of mismatch with v1.
> According to
> http://docs.oracle.com/javase/6/docs/technotes/tools/windows/classpath.html
> ("Understanding class path wildcards")
> "The order in which the JAR files in a directory are enumerated in the
> expanded class path is not specified and may vary from platform to platform
> and even from moment to moment on the same machine."
> Suggest distcpv1 be deprecated at this point, possibly by discontinuing build
> of distcpv1.
--
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
