[jira] [Updated] (HADOOP-7549) Use JDK ServiceLoader mechanism to find FileSystem implementations
[ https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated HADOOP-7549: --- Resolution: Fixed Fix Version/s: (was: 0.24.0) 2.0.0 Hadoop Flags: Reviewed Status: Resolved (was: Patch Available) committed to trunk and branch-2. (committed v2 as v3 which is identical was missing the service files) Use JDK ServiceLoader mechanism to find FileSystem implementations -- Key: HADOOP-7549 URL: https://issues.apache.org/jira/browse/HADOOP-7549 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 0.23.0 Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 2.0.0 Attachments: HADOOP-7549v1.patch, HADOOP-7549v2.patch, HADOOP-7549v3.patch Currently configuring FileSystem implementations must be done by declaring the FileSystem class in the Hadoop configuration files (core-default.xml, ...). Using JDK ServiceLoader mechanism this configuration step can be avoided. Adding the JAR file with the additional FileSystem implementation would suffice. This is similar to what is being proposed for compression codecs (HADOOP-7350). -- 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-7549) Use JDK ServiceLoader mechanism to find FileSystem implementations
[
https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-7549:
---
Attachment: HDFS-7549v3.patch
rebasing to trunk to remove patch complains.
I've run test-patch locally with and without the patch and I get the same
number of warnings:
{code}
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 2 new or modified test
files.
-1 javadoc. The javadoc tool appears to have generated 8 warning messages.
-1 javac. The applied patch generated 1707 javac compiler warnings (more
than the trunk's current 1706 warnings).
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to introduce 20 new Findbugs (version
1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
{code}
Use JDK ServiceLoader mechanism to find FileSystem implementations
--
Key: HADOOP-7549
URL: https://issues.apache.org/jira/browse/HADOOP-7549
Project: Hadoop Common
Issue Type: Improvement
Components: fs
Affects Versions: 0.23.0
Reporter: Alejandro Abdelnur
Assignee: Alejandro Abdelnur
Fix For: 0.24.0
Attachments: HADOOP-7549v1.patch, HADOOP-7549v2.patch
Currently configuring FileSystem implementations must be done by declaring
the FileSystem class in the Hadoop configuration files (core-default.xml,
...).
Using JDK ServiceLoader mechanism this configuration step can be avoided.
Adding the JAR file with the additional FileSystem implementation would
suffice.
This is similar to what is being proposed for compression codecs
(HADOOP-7350).
--
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-7549) Use JDK ServiceLoader mechanism to find FileSystem implementations
[ https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated HADOOP-7549: --- Attachment: (was: HDFS-7549v3.patch) Use JDK ServiceLoader mechanism to find FileSystem implementations -- Key: HADOOP-7549 URL: https://issues.apache.org/jira/browse/HADOOP-7549 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 0.23.0 Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.24.0 Attachments: HADOOP-7549v1.patch, HADOOP-7549v2.patch Currently configuring FileSystem implementations must be done by declaring the FileSystem class in the Hadoop configuration files (core-default.xml, ...). Using JDK ServiceLoader mechanism this configuration step can be avoided. Adding the JAR file with the additional FileSystem implementation would suffice. This is similar to what is being proposed for compression codecs (HADOOP-7350). -- 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-7549) Use JDK ServiceLoader mechanism to find FileSystem implementations
[ https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated HADOOP-7549: --- Attachment: HADOOP-7549v3.patch reattaching with correct patch filename Use JDK ServiceLoader mechanism to find FileSystem implementations -- Key: HADOOP-7549 URL: https://issues.apache.org/jira/browse/HADOOP-7549 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 0.23.0 Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.24.0 Attachments: HADOOP-7549v1.patch, HADOOP-7549v2.patch, HADOOP-7549v3.patch Currently configuring FileSystem implementations must be done by declaring the FileSystem class in the Hadoop configuration files (core-default.xml, ...). Using JDK ServiceLoader mechanism this configuration step can be avoided. Adding the JAR file with the additional FileSystem implementation would suffice. This is similar to what is being proposed for compression codecs (HADOOP-7350). -- 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-7549) Use JDK ServiceLoader mechanism to find FileSystem implementations
[ https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated HADOOP-7549: --- Attachment: HADOOP-7549v2.patch Patch rebased to trunk. It keeps current mappings in the services definition (it was been done already). Definition in configuration overrides a service definition (it was been done already). It removes the deprecated warning log when resolving a FS implementation from configuration as this is the way of overriding an implementation, thus it is not deprecated. It adds HAR and WebHdfs filesystems to the service loading mechanism/definitions. Use JDK ServiceLoader mechanism to find FileSystem implementations -- Key: HADOOP-7549 URL: https://issues.apache.org/jira/browse/HADOOP-7549 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 0.23.0 Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.24.0 Attachments: HADOOP-7549v1.patch, HADOOP-7549v2.patch Currently configuring FileSystem implementations must be done by declaring the FileSystem class in the Hadoop configuration files (core-default.xml, ...). Using JDK ServiceLoader mechanism this configuration step can be avoided. Adding the JAR file with the additional FileSystem implementation would suffice. This is similar to what is being proposed for compression codecs (HADOOP-7350). -- 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-7549) Use JDK ServiceLoader mechanism to find FileSystem implementations
[ https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated HADOOP-7549: --- Attachment: HADOOP-7549v1.patch Use JDK ServiceLoader mechanism to find FileSystem implementations -- Key: HADOOP-7549 URL: https://issues.apache.org/jira/browse/HADOOP-7549 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 0.23.0 Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.23.0 Attachments: HADOOP-7549v1.patch Currently configuring FileSystem implementations must be done by declaring the FileSystem class in the Hadoop configuration files (core-default.xml, ...). Using JDK ServiceLoader mechanism this configuration step can be avoided. Adding the JAR file with the additional FileSystem implementation would suffice. This is similar to what is being proposed for compression codecs (HADOOP-7350). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HADOOP-7549) Use JDK ServiceLoader mechanism to find FileSystem implementations
[ https://issues.apache.org/jira/browse/HADOOP-7549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Abdelnur updated HADOOP-7549: --- Status: Patch Available (was: Open) Use JDK ServiceLoader mechanism to find FileSystem implementations -- Key: HADOOP-7549 URL: https://issues.apache.org/jira/browse/HADOOP-7549 Project: Hadoop Common Issue Type: Improvement Components: fs Affects Versions: 0.23.0 Reporter: Alejandro Abdelnur Assignee: Alejandro Abdelnur Fix For: 0.23.0 Attachments: HADOOP-7549v1.patch Currently configuring FileSystem implementations must be done by declaring the FileSystem class in the Hadoop configuration files (core-default.xml, ...). Using JDK ServiceLoader mechanism this configuration step can be avoided. Adding the JAR file with the additional FileSystem implementation would suffice. This is similar to what is being proposed for compression codecs (HADOOP-7350). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
