[jira] [Created] (HADOOP-8606) FileSystem.get may return the wrong filesystem
Daryn Sharp created HADOOP-8606:
---
Summary: FileSystem.get may return the wrong filesystem
Key: HADOOP-8606
URL: https://issues.apache.org/jira/browse/HADOOP-8606
Project: Hadoop Common
Issue Type: Bug
Components: fs
Affects Versions: 2.0.0-alpha, 0.23.0, 1.0.0, 3.0.0
Reporter: Daryn Sharp
Assignee: Daryn Sharp
{{FileSystem.get(URI, conf)}} will return the default fs if the scheme is null,
regardless of whether the authority is null too. This causes URIs of
"//authority/path" to _always_ refer to "/path" on the default fs. To the
user, this appears to "work" if the authority in the null-scheme URI matches
the authority of the default fs. When the authorities don't match, the user is
very surprised that the default fs is used.
--
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] [Created] (HADOOP-8607) Replace references to "Dr Who" in codebase with @BigDataBorat
Steve Loughran created HADOOP-8607:
--
Summary: Replace references to "Dr Who" in codebase with
@BigDataBorat
Key: HADOOP-8607
URL: https://issues.apache.org/jira/browse/HADOOP-8607
Project: Hadoop Common
Issue Type: Improvement
Components: util
Affects Versions: 2.0.0-alpha, 1.0.3
Reporter: Steve Loughran
Priority: Minor
People complain that having "Dr Who" in the code causes confusion and isn't
appropriate in Hadoop now that it has matured.
I propose that we replace this anonymous user ID with {{@BigDataBorat}}. This
will
# Increase brand awareness of @BigDataBorat and their central role in the Big
Data ecosystem.
# Drive traffic to twitter, and increase their revenue. As contributors to the
Hadoop platform, this will fund further Hadoop development.
Patching the code is straightforward; no easy tests, though we could monitor
twitter followers to determine rollout of the patch in the field.
--
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] [Created] (HADOOP-8608) Add Configuration API for parsing time durations
Todd Lipcon created HADOOP-8608:
---
Summary: Add Configuration API for parsing time durations
Key: HADOOP-8608
URL: https://issues.apache.org/jira/browse/HADOOP-8608
Project: Hadoop Common
Issue Type: Improvement
Components: conf
Affects Versions: 3.0.0
Reporter: Todd Lipcon
Hadoop has a lot of configurations which specify durations or intervals of
time. Unfortunately these different configurations have little consistency in
units - eg some are in milliseconds, some in seconds, and some in minutes. This
makes it difficult for users to configure, since they have to always refer back
to docs to remember the unit for each property.
The proposed solution is to add an API like {{Configuration.getTimeDuration}}
which allows the user to specify the units with a prefix. For example, "10ms",
"10s", "10m", "10h", or even "10d". For backwards-compatibility, if the user
does not specify a unit, the API can specify the default unit, and warn the
user that they should specify an explicit unit instead.
--
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
