Possibly the reason for Stack's consternation is that this is a
Hadoop-specific versioning scheme, rather than a standard one like
Semantic Versioning (http://semver.org/) which is more widely
understood.
With that scheme we would have something like
2.0.0-alpha, 2.0.0-alpha.1, 2.0.0-alpha.2, 2
On Wed, Jan 30, 2013 at 11:32 PM, Vinod Kumar Vavilapalli
wrote:
> I still have a list of pending API/protocol cleanup in YARN that need to be
> in before we even attempt supporting compatibility further down the road.
To let others track these it would be useful if they were tagged in
JIRA with
+1
Checked sigs and checksums, source tag, and built from source.
Cheers,
Tom
On Fri, Apr 12, 2013 at 2:56 PM, Arun C Murthy wrote:
> Folks,
>
> I've created a release candidate (RC2) for hadoop-2.0.4-alpha that I would
> like to release.
>
> The RC is available at:
> http://people.apache.org
Hi Arun,
A couple more issues that I think are blockers:
HADOOP-7782 (Aggregate project javadocs) should be a blocker since
otherwise private APIs are published as a part of the public API.
MAPREDUCE-3237 (Move LocalJobRunner to hadoop-mapreduce-client-core
module) is also a blocker since without
+1
Tom
On Fri, Jun 26, 2009 at 8:13 AM, Chris Douglas wrote:
> +1
>
> On Thu, Jun 25, 2009 at 11:42 PM, Nigel Daley wrote:
>> Here are some logos for the new subprojects
>> http://www.flickr.com/photos/88199...@n00/3661433605/
>>
>> Please vote +1 if you like 'em and -1 if you don't.
>>
>> Cheers
Here's my (single) slide about the 0.21 release.
Tom
On Thu, May 6, 2010 at 5:38 PM, Arun C Murthy wrote:
> # Shared goals
> - Hadoop is HDFS & Map-Reduce in this context of this set of slides
> # Priorities
> * Yahoo
> - Correctness
> - Availability: Not the same as high-availability (6
see SVN commit r775220 - so I
wasn't able to post the slide there either.)
Tom
On Fri, May 7, 2010 at 9:36 AM, Tom White wrote:
> Here's my (single) slide about the 0.21 release.
>
> Tom
>
> On Thu, May 6, 2010 at 5:38 PM, Arun C Murthy wrote:
>> # Shared goals
>
The work in https://issues.apache.org/jira/browse/HDFS-2096 is ready
to be committed, so unless there are any objections I will do so on
Monday at 5pm UTC (that's 10am PDT, http://s.apache.org/o6F).
I'll also create a script to convert patches to the new layout, and
switch over the Jenkins jobs th
are very close to getting the
> merge done. We should call a vote asap. By holding off it the mvn patch it
> will save us a bit of time - we spent at more than a couple of days on
> resolving after the common mvn'ization.
>
> Thanks for understanding.
>
> Arun
>
> On Au
k' and
> should be done by tmrw.
>
> Also, can you guys please ensure that secure HDFS works after mvn'ization?
>
> thanks,
> Arun
>
> On Aug 13, 2011, at 9:39 PM, Tom White wrote:
>
>> Hi Arun,
>>
>> I'm fine with that. When do you expect
soon (e.g.
HADOOP-7498, HADOOP-7496, MAPREDUCE-2856), but these shouldn't stop
folks from doing development as usual.
Thanks to everyone who helped with this!
Cheers,
Tom
On Thu, Aug 18, 2011 at 11:30 AM, Tom White wrote:
> Now that MR-279 has been merged into trunk, I plan to commit
[
https://issues.apache.org/jira/browse/HDFS-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-321.
Resolution: Implemented
The contract tests have been greatly expanded by Steve L since I opened this,
so
Log the filename when file locking fails
Key: HDFS-844
URL: https://issues.apache.org/jira/browse/HDFS-844
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: Tom White
nents: build
Reporter: Tom White
Assignee: Tom White
HDFS companion issue for HADOOP-6407.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
: Tom White
See http://hudson.zones.apache.org/hudson/view/Hadoop/job/Hadoop-Hdfs-trunk/ -
it's been broken since the end of January. Looks like a problem in the HDFS
proxy contrib build.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment t
Issue Type: Improvement
Reporter: Tom White
Priority: Blocker
Fix For: 0.21.0
This is the HDFS part of HADOOP-6404.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Fix references to 0.22 in 0.21 branch
-
Key: HDFS-1173
URL: https://issues.apache.org/jira/browse/HDFS-1173
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Tom White
Assignee: Tom
[
https://issues.apache.org/jira/browse/HDFS-1173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-1173.
-
Resolution: Fixed
I've just committed this.
> Fix references to 0.22 in 0.2
[
https://issues.apache.org/jira/browse/HDFS-1126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-1126.
-
Hadoop Flags: [Reviewed]
Resolution: Fixed
I've just committed this.
> Change HDFS to d
Reporter: Tom White
Assignee: Tom White
Priority: Blocker
Fix For: 0.21.0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Reporter: Tom White
Assignee: Tom White
Priority: Blocker
Fix For: 0.21.0
HDFS part of HADOOP-6800.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
test-libhdfs.sh fails
-
Key: HDFS-1255
URL: https://issues.apache.org/jira/browse/HDFS-1255
Project: Hadoop HDFS
Issue Type: Bug
Components: test
Reporter: Tom White
Assignee: Tom White
[
https://issues.apache.org/jira/browse/HDFS-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-609.
Hadoop Flags: [Reviewed]
Fix Version/s: (was: 0.22.0)
Resolution: Fixed
I've committed
libhdfs is missing from the tarball
---
Key: HDFS-1256
URL: https://issues.apache.org/jira/browse/HDFS-1256
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Tom White
Priority: Blocker
fuse-dfs does not compile
-
Key: HDFS-1267
URL: https://issues.apache.org/jira/browse/HDFS-1267
Project: Hadoop HDFS
Issue Type: Bug
Components: contrib/fuse-dfs
Reporter: Tom White
Issue Type: Bug
Components: build
Reporter: Tom White
Assignee: Giridharan Kesavan
Priority: Blocker
Fix For: 0.21.0
HDFS companion issue to HADOOP-6847.
--
This message is automatically generated by JIRA.
-
You can reply to this
[
https://issues.apache.org/jira/browse/HDFS-1288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-1288.
-
Resolution: Cannot Reproduce
> start-all.sh / stop-all.sh does not seem to work with H
Remove empty java files
---
Key: HDFS-1349
URL: https://issues.apache.org/jira/browse/HDFS-1349
Project: Hadoop HDFS
Issue Type: Bug
Affects Versions: 0.21.0
Reporter: Tom White
Doug identified some
[
https://issues.apache.org/jira/browse/HDFS-1422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-1422.
-
Resolution: Fixed
HADOOP-6951 has now been reverted and I confirmed HDFS trunk now compiles.
Sorry for
[
https://issues.apache.org/jira/browse/HDFS-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-1416.
-
Resolution: Fixed
Assignee: Tom White
I've fixed this.
> CHANGES.txt does not reflect the
Add integration test for Ganglia 3.1
Key: HDFS-1493
URL: https://issues.apache.org/jira/browse/HDFS-1493
Project: Hadoop HDFS
Issue Type: Test
Components: test
Reporter: Tom White
Allow TestHDFSCLI to be run against a cluster
-
Key: HDFS-1762
URL: https://issues.apache.org/jira/browse/HDFS-1762
Project: Hadoop HDFS
Issue Type: Test
Reporter: Tom White
TestHDFSCLI fails due to typo in expected output
-
Key: HDFS-1909
URL: https://issues.apache.org/jira/browse/HDFS-1909
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Tom White
[
https://issues.apache.org/jira/browse/HDFS-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-1909.
-
Resolution: Fixed
Hadoop Flags: [Reviewed]
I've just committed this to the 0.22 b
start-dfs.sh script fails for tarball install
-
Key: HDFS-2323
URL: https://issues.apache.org/jira/browse/HDFS-2323
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Tom White
Javadoc generation hangs
Key: HDFS-2640
URL: https://issues.apache.org/jira/browse/HDFS-2640
Project: Hadoop HDFS
Issue Type: Bug
Reporter: Tom White
Typing 'mvn javadoc:javadoc' causes th
[
https://issues.apache.org/jira/browse/HDFS-2640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-2640.
-
Resolution: Fixed
Fix Version/s: 0.23.1
0.24.0
Assignee: Tom White
[
https://issues.apache.org/jira/browse/HDFS-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HDFS-83.
---
Resolution: Duplicate
> Move fs.checkpoint.* properties to hdfs-default.
: Improvement
Components: documentation
Reporter: Tom White
Port HADOOP-6668 to branch-1
--
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
: hdfs client
Affects Versions: 0.23.1
Reporter: Tom White
When hadoop.rpc.socket.factory.class.default is set to
org.apache.hadoop.net.SocksSocketFactory, HDFS file reads fail with errors like
{noformat}
Socket Socket[addr=/10.12.185.132,port=50010,localport=55216] does not have an
40 matches
Mail list logo
