[
https://issues.apache.org/jira/browse/HADOOP-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-3494.
---
Resolution: Invalid
Improve S3FileSystem data integrity using MD5 checksums
[
https://issues.apache.org/jira/browse/HADOOP-3495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-3495.
---
Resolution: Won't Fix
Resolving this since as Ken points out we should let S3 report the problem
On behalf of the Apache Hadoop PMC, I'm pleased to announce the
addition of the following new Hadoop PMC members:
* Daryn Sharp
* Hitesh Shah
* Jonathan Eagles
* Kihwal Lee
* Luke Lu
* Steve Loughran
* Uma Maheswara Rao G
Thank you for all of your work on the project! Please join me in welcoming
+1
Cheers,
Tom
On Tue, May 21, 2013 at 10:10 PM, Matt Foley ma...@apache.org wrote:
Hi all,
This has been a side topic in several email threads recently. Currently we
have an ambiguity. We have a tradition in the dev community that any
committer can create a branch, and propose release
+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 a...@hortonworks.com 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:
[
https://issues.apache.org/jira/browse/HADOOP-9124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-9124.
---
Resolution: Fixed
Fix Version/s: 1.2.0
Committed to branch 1
There are some tests like the S3 tests that end with Test (e.g.
Jets3tNativeS3FileSystemContractTest) - unlike normal tests which
start with Test. Only those that start with Test are run
automatically (see the surefire configuration in
hadoop-project/pom.xml). You have to run the others manually
+1, +1, -1
Tom
On Sat, Nov 24, 2012 at 8:13 PM, Matt Foley ma...@apache.org wrote:
For discussion, please see previous thread [PROPOSAL] introduce Python as
build-time and run-time dependency for Hadoop and throughout Hadoop stack.
This vote consists of three separate items:
1.
Tom White created HADOOP-9097:
-
Summary: Maven RAT plugin is not checking all source files
Key: HADOOP-9097
URL: https://issues.apache.org/jira/browse/HADOOP-9097
Project: Hadoop Common
Issue
[
https://issues.apache.org/jira/browse/HADOOP-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-8860.
---
Resolution: Fixed
Fix Version/s: 0.23.5
I just pulled this into 0.23 too after discussing
Tom White created HADOOP-8852:
-
Summary: DelegationTokenRenewer thread is not stopped when its
filesystem is closed
Key: HADOOP-8852
URL: https://issues.apache.org/jira/browse/HADOOP-8852
Project: Hadoop
Tom White created HADOOP-8825:
-
Summary: Reinstate constructors in
SequenceFile.BlockCompressWriter and SequenceFile.RecordCompressWriter for
compatibility with Hadoop 1
Key: HADOOP-8825
URL: https
Tom White created HADOOP-8762:
-
Summary: Mark container-provided dependencies with 'provided' scope
Key: HADOOP-8762
URL: https://issues.apache.org/jira/browse/HADOOP-8762
Project: Hadoop Common
You need to create a Jenkins job for the project (named
PreCommit-Oozie-Build) which runs every 10 minutes and runs a JIRA
query to find new patches. See
https://builds.apache.org//job/PreCommit-Admin/ for instructions.
Cheers,
Tom
On Fri, Aug 17, 2012 at 3:07 AM, Alejandro Abdelnur
[
https://issues.apache.org/jira/browse/HADOOP-5754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-5754.
---
Resolution: Fixed
Add link to training from website
[
https://issues.apache.org/jira/browse/HADOOP-8530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-8530.
---
Resolution: Duplicate
Fixed by HADOOP-8533.
Potential deadlock in IPC
Tom White created HADOOP-8530:
-
Summary: Potential deadlock in IPC
Key: HADOOP-8530
URL: https://issues.apache.org/jira/browse/HADOOP-8530
Project: Hadoop Common
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HADOOP-6799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-6799.
---
Resolution: Duplicate
This is being fixed in HADOOP-8522.
GzipCodec
Tom White created HADOOP-8354:
-
Summary: test-patch findbugs may fail if a dependent module is
changed
Key: HADOOP-8354
URL: https://issues.apache.org/jira/browse/HADOOP-8354
Project: Hadoop Common
Tom White created HADOOP-8328:
-
Summary: Duplicate FileSystem Statistics object for 'file' scheme
Key: HADOOP-8328
URL: https://issues.apache.org/jira/browse/HADOOP-8328
Project: Hadoop Common
Just to be clear, the HADOOP-8308 patch is selective about which tests
it runs, so it doesn't increase build run times. Unless there are any
objections, I'd like to commit the patch and switch Jenkins to run
from the top-level directory early next week.
Cheers,
Tom
On Fri, Apr 27, 2012 at 2:21
I have a patch at https://issues.apache.org/jira/browse/HADOOP-8308
which takes the approach that Alejandro outlined.
Cheers,
Tom
On Wed, Apr 18, 2012 at 10:11 AM, Alejandro Abdelnur t...@cloudera.com wrote:
Giri,
On Tue, Apr 17, 2012 at 8:36 PM, Giridharan Kesavan
gkesa...@hortonworks.com
Tom White created HADOOP-8308:
-
Summary: Support cross-project Jenkins builds
Key: HADOOP-8308
URL: https://issues.apache.org/jira/browse/HADOOP-8308
Project: Hadoop Common
Issue Type: Task
Giri,
I think Aaron was talking about not running all test cases for changes
to any project (e.g. HDFS and MapReduce). My proposal was to run all
the tests for any Common change. An HDFS change would only run HDFS
tests, and any MapReduce change would only run MapReduce tests.
Another thing I
Currently Jenkins QA builds don't support cross-project patches, since
they try to apply them to the hadoop-{common,hdfs,mapreduce}-project
tree, and reject any patches that are not strictly confined to that
tree. For changes that span projects (e.g. moving code from HDFS or MR
to Common, or build
Components: build
Reporter: Tom White
As mentioned by Scott Carey in
https://issues.apache.org/jira/browse/MAPREDUCE-3378?focusedCommentId=13173437page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13173437,
we need to make sure that components
TestHealthMonitor fails occasionally
-
Key: HADOOP-8204
URL: https://issues.apache.org/jira/browse/HADOOP-8204
Project: Hadoop Common
Issue Type: Bug
Reporter: Tom White
See e.g.
https
+1
Checked signatures and checksums, also ran a few jobs successfully.
Tom
On Tue, Feb 14, 2012 at 2:29 PM, Matt Foley ma...@apache.org wrote:
Hi all,
Hadoop-1.0.1-rc1 is now available at
http://people.apache.org/~mattf/hadoop-1.0.1-rc1/
Please download it, test it, and vote on whether
[
https://issues.apache.org/jira/browse/HADOOP-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7767.
---
Resolution: Duplicate
Fix Version/s: (was: 0.24.0)
This was fixed in HADOOP-7763
[
https://issues.apache.org/jira/browse/HADOOP-6437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-6437.
---
Resolution: Not A Problem
HOD was removed in HADOOP-7137.
HOD tests are not being
Arun,
There are instructions on how to run 0.23/trunk from the dev tree here:
http://wiki.apache.org/hadoop/HowToSetupYourDevelopmentEnvironment#Run_HDFS_in_pseudo-distributed_mode_from_the_dev_tree
Type: 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
+1
I verified checksums and signatures, and successfully ran some MapReduce jobs.
I also ran an API compatibility check against the previous release
(https://issues.apache.org/jira/browse/HADOOP-7035) and it passed.
Cheers,
Tom
On Fri, Dec 16, 2011 at 12:10 PM, Matt Foley
Upgrade to Avro 1.5.4
-
Key: HADOOP-7883
URL: https://issues.apache.org/jira/browse/HADOOP-7883
Project: Hadoop Common
Issue Type: Improvement
Affects Versions: 0.23.0
Reporter: Tom White
: build
Affects Versions: 0.23.0
Reporter: Tom White
They are missing from the bin directory.
--
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
[
https://issues.apache.org/jira/browse/HADOOP-7826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7826.
---
Resolution: Invalid
These scripts are in sbin. However, the yarn equivalents should be moved from
Reporter: Tom White
Only 32-bit libraries are included
--
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
[
https://issues.apache.org/jira/browse/HADOOP-7433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7433.
---
Resolution: Duplicate
Fix Version/s: (was: 0.24.0)
See HADOOP-7807
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
[
https://issues.apache.org/jira/browse/HADOOP-7768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7768.
---
Resolution: Fixed
Fix Version/s: 0.24.0
Target Version/s: 0.23.0, 0.24.0
TestJMXJsonServlet is failing
-
Key: HADOOP-7769
URL: https://issues.apache.org/jira/browse/HADOOP-7769
Project: Hadoop Common
Issue Type: Bug
Reporter: Tom White
The testQury (sic) test is failing
[
https://issues.apache.org/jira/browse/HADOOP-7564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7564.
---
Resolution: Fixed
Fix Version/s: 0.24.0
0.23.0
Hadoop Flags: Reviewed
[
https://issues.apache.org/jira/browse/HADOOP-7497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7497.
---
Resolution: Duplicate
This was fixed by HADOOP-7737.
Make hadoop scripts to work
+1
Checksums and signatures were OK.
I also ran an API compatibility check
(https://issues.apache.org/jira/browse/HADOOP-7035,
https://github.com/tomwhite/hadoop-compatibility-tools) and it passed.
There were three errors, all false positives:
Class org.apache.hadoop.fs.HarFileSystem
E1.2 -
I think it's simplest to publish a single Hadoop tarball and users
start the services they want. This is the model we have always
followed up to now.
Cheers,
Tom
On Wed, Oct 12, 2011 at 9:07 AM, Alejandro Abdelnur t...@cloudera.com wrote:
Currently common, hdfs and mapred create partial tars
Type: Improvement
Reporter: Tom White
Assignee: Tom White
Priority: Blocker
Fix For: 0.23.0
0.20.20x to 0.23.0 will be a common upgrade path, so we should document any
incompatible API changes that will affect users.
--
This message
[
https://issues.apache.org/jira/browse/HADOOP-7612?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7612.
---
Resolution: Fixed
Fix Version/s: 0.23.0
Hadoop Flags: [Reviewed]
I've just committed
Type: Bug
Components: build
Reporter: Tom White
Assignee: Tom White
After a change is committed the corresponding JIRA is updated with multiple
comments saying the same thing. E.g.
https://issues.apache.org/jira/browse/HADOOP-7612?focusedCommentId=13100560page
Components: build
Reporter: Tom White
Assignee: Tom White
HADOOP-7561 changed the behaviour of test-patch to run tests for changed
modules, however this was assuming a flat structure. Given the nested maven
hierarchy we should always run all the common tests for any common
[
https://issues.apache.org/jira/browse/HADOOP-7587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7587.
---
Resolution: Duplicate
Duplicate of HADOOP-7576
hadoop-auth module has 4 findbugs warnings
[
https://issues.apache.org/jira/browse/HADOOP-7561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7561.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I've just committed this.
Make test-patch only
Reporter: Tom White
Found in HADOOP-7567:
https://builds.apache.org/job/PreCommit-HADOOP-Build/65//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-alfredo.html
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com
Remove test-patch SVN externals
---
Key: HADOOP-7564
URL: https://issues.apache.org/jira/browse/HADOOP-7564
Project: Hadoop Common
Issue Type: Sub-task
Reporter: Tom White
With the new top-level
: Tom White
Assignee: Tom White
Fix For: 0.23.0
By running test-patch from trunk we can check that a change in one project
(e.g. common) doesn't cause compile errors in other projects (e.g. HDFS). To
get this to work we only need to run tests for the modules
[
https://issues.apache.org/jira/browse/HADOOP-7525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7525.
---
Resolution: Fixed
Fix Version/s: 0.23.0
Hadoop Flags: [Reviewed]
I've just committed
[
https://issues.apache.org/jira/browse/HADOOP-7500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7500.
---
Resolution: Fixed
I don't think this needs to be committed since it's only useful for a limited
Make arguments to test-patch optional
-
Key: HADOOP-7525
URL: https://issues.apache.org/jira/browse/HADOOP-7525
Project: Hadoop Common
Issue Type: Sub-task
Reporter: Tom White
Currently you
[
https://issues.apache.org/jira/browse/HADOOP-7515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7515.
---
Resolution: Fixed
Hadoop Flags: [Reviewed]
I've just committed this.
test-patch reports
Components: build
Reporter: Tom White
Assignee: Tom White
Fix For: 0.23.0
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reporter: Tom White
Assignee: Tom White
We need an equivalent of https://builds.apache.org/job/PreCommit-HADOOP-Build
for the Maven build. Until this is live it would be triggered manually and
wouldn't post comments to JIRA.
--
This message is automatically generated by JIRA
Components: conf, io
Reporter: Tom White
By using a ServiceLoader users wouldn't have to add codec classes to
io.compression.codecs for codecs that aren't shipped with Hadoop (e.g. LZO),
since they would be automatically picked up from the classpath.
--
This message
[
https://issues.apache.org/jira/browse/HADOOP-7283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-7283.
---
Resolution: Fixed
Assignee: Tom White
The build at
https://builds.apache.org/hudson/view/G-L
Type: Task
Components: build
Reporter: Tom White
Priority: Blocker
Fix For: 0.22.0
The job at
https://builds.apache.org/hudson/view/G-L/view/Hadoop/job/Hadoop-22-Build/ is
building tarballs, but they do not currently include both 32-bit and 64-bit
On Mon, May 2, 2011 at 12:16 PM, Eli Collins e...@cloudera.com wrote:
On Fri, Apr 29, 2011 at 4:09 PM, Owen O'Malley omal...@apache.org wrote:
I think everything is ready to go on the 0.20.203.0 release. It includes
security and a lot of improvements in the capacity scheduler and JobTracker.
Components: documentation
Reporter: Tom White
Assignee: Tom White
Priority: Blocker
Fix For: 0.22.0
Common counterpart of HDFS-671.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software
[
https://issues.apache.org/jira/browse/HADOOP-6953?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-6953.
---
Resolution: Duplicate
Fix Version/s: (was: 0.21.1)
start-{dfs,mapred}.sh scripts fail
[
https://issues.apache.org/jira/browse/HADOOP-6734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-6734.
---
Resolution: Duplicate
Jets3tNativeFileSystemStore wrongly calls S3Service.createBucket during
Issue Type: Improvement
Components: conf, filecache
Reporter: Tom White
Assignee: Tom White
Attachments: HADOOP-7112.patch
In GenericOptionsParser#getLibJars() any jars that are not local filesystem
paths are silently ignored. We should issue
: Improvement
Components: conf
Reporter: Tom White
Currently each class with a main() method (in HDFS and MapReduce) calls
Configuration.addDefaultResource() to add the names of resource files to load
(e.g. see DataNode and NameNode which both add hdfs-default.xml and
hdfs
[
https://issues.apache.org/jira/browse/HADOOP-6776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-6776.
---
Resolution: Duplicate
UserGroupInformation.createProxyUser's javadoc is broken
[
https://issues.apache.org/jira/browse/HADOOP-6917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-6917.
---
Resolution: Duplicate
Fixed in HADOOP-6818
Remove empty FTPFileSystemConfigKeys.java file
[
https://issues.apache.org/jira/browse/HADOOP-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White reopened HADOOP-6663:
---
Re-opening as there was a compilation problem.
BlockDecompressorStream get EOF exception when
Components: scripts
Affects Versions: 0.21.0
Reporter: Tom White
Fix For: 0.21.1
If the HADOOP_HOME environment variable is not set then the start and stop
scripts for HDFS and MapReduce fail with Hadoop common not found.. The
start-all.sh and stop-all.sh scripts
Components: build
Affects Versions: 0.21.0
Reporter: Tom White
Assignee: Tom White
Fix For: 0.21.1
When you try to close the staging repository to make it visible to the public
the operation fails (see
https://issues.apache.org/jira/browse/HDFS
Components: fs
Reporter: Tom White
Assignee: Tom White
Priority: Minor
It should be named markSupported to override the method defined in InputStream.
Since it doesn't change the default no harm is done.
--
This message is automatically generated
Hi everyone,
I am pleased to announce that Apache Hadoop 0.21.0 is available for
download from http://hadoop.apache.org/common/releases.html.
Over 1300 issues have been addressed since 0.20.2; you can find details at
http://hadoop.apache.org/common/docs/r0.21.0/releasenotes.html
Reporter: Tom White
FTPFileSystemConfigKeys.java is empty and not used so should be deleted.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
On Fri, Aug 20, 2010 at 10:32 AM, Doug Cutting cutt...@apache.org wrote:
+1
I verified the checksum signature and ran some of the example programs. I
also ran RAT to check that sources are licensed correctly.
I only examined the merged artifact. Do we need to release the others?
I think
+1 Based on running a job in pseudo-distributed mode, and checking the
signature and checksum.
Tom
On Mon, Aug 16, 2010 at 10:29 PM, Tom White t...@cloudera.com wrote:
I have created a new candidate build for Hadoop 0.21.0. This fixes
MAPREDUCE-2012 and MAPREDUCE-2014 which were found
I have created a new candidate build for Hadoop 0.21.0. This fixes
MAPREDUCE-2012 and MAPREDUCE-2014 which were found for the previous
release candidate (1).
This release is being classified as a minor release, which means that
it is API compatible with 0.20.2.
*** This release candidate has not
I have created a new candidate build for Hadoop 0.21.0. This fixes
MAPREDUCE-1920 and MAPREDUCE-1926 which were found for the previous
release candidate (0).
This release is being classified as a minor release, which means that
it is API compatible with 0.20.2.
*** This release candidate has not
I just committed MAPREDUCE-1876 to branch 0.21. The fix for
MAPREDUCE-1980 can go into branch 0.21 when it's done.
Cheers,
Tom
On Sun, Aug 1, 2010 at 8:52 PM, Amareshwari Sri Ramadasu
amar...@yahoo-inc.com wrote:
The problem is reported and fixed in MAPREDUCE-1876, but it is not committed
to
, Jul 8, 2010 at 8:13 PM, Tom White t...@cloudera.com wrote:
A problem was found with Job.getCounters() returning null (see
https://issues.apache.org/jira/browse/MAPREDUCE-1920). I plan to roll
a new release candidate when this is fixed.
Cheers,
Tom
On Fri, Jul 2, 2010 at 8:25 AM, Tom White
I have created a candidate build for Hadoop 0.21.0. This fixes over
one thousand issues in Common, HDFS, and MapReduce since 0.20.2.
This release is being classified as a minor release, which means that
it is API compatible with 0.20.2.
*** This release candidate has not been tested extensively,
Reporter: Tom White
Assignee: Tom White
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Common
Issue Type: Improvement
Components: build, documentation
Reporter: Tom White
Some links:
*
http://eclipsesource.com/blogs/2010/06/14/api_tools_top_eclipse_helios_feature_8/
* http://wiki.eclipse.org/PDE/API_Tools
--
This message is automatically generated
Components: fs
Reporter: Tom White
Assignee: Tom White
Priority: Blocker
Fix For: 0.21.0
As discussed in HDFS-609 and HADOOP-5438 we should back out the FileSystem
create() method that takes a set of CreateFlag objects, until the interface has
been agreed
Harmonize JAR library versions
--
Key: HADOOP-6800
URL: https://issues.apache.org/jira/browse/HADOOP-6800
Project: Hadoop Common
Issue Type: Bug
Reporter: Tom White
Priority: Blocker
[
https://issues.apache.org/jira/browse/HADOOP-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-6785.
---
Resolution: Invalid
This turned out not to be a problem (see HADOOP-6773).
Fix references to 0.22
Fix references to 0.22 in 0.21 branch
-
Key: HADOOP-6785
URL: https://issues.apache.org/jira/browse/HADOOP-6785
Project: Hadoop Common
Issue Type: Bug
Reporter: Tom White
Assignee
Here's my (single) slide about the 0.21 release.
Tom
On Thu, May 6, 2010 at 5:38 PM, Arun C Murthy acmur...@gmail.com wrote:
# Shared goals
- Hadoop is HDFS Map-Reduce in this context of this set of slides
# Priorities
* Yahoo
- Correctness
- Availability: Not the same as
It's in https://issues.apache.org/jira/browse/HADOOP-2141, which will
be in 0.21.
Cheers,
Tom
On Thu, May 6, 2010 at 9:53 AM, Allen Wittenauer
awittena...@linkedin.com wrote:
On May 5, 2010, at 11:36 PM, momina khan wrote:
hi could anyone point me to where i can download the LATE scheduler
Hi everyone,
As previously announced the feature freeze date for 0.21 is tomorrow,
Friday 30 April at 5pm PDT. After this time I'll recreate the 0.21
branches in core, HDFS and MapReduce. Once the branches have been made
I would encourage everyone to review and fix the blockers
Move cluster_setup.xml from MapReduce to Common
---
Key: HADOOP-6738
URL: https://issues.apache.org/jira/browse/HADOOP-6738
Project: Hadoop Common
Issue Type: Test
Reporter: Tom White
-task
Components: fs
Reporter: Tom White
Priority: Blocker
Fix For: 0.21.0
We should have an automated test for checking that programs written against an
old version of the FileSystem API still run with a newer version.
--
This message
[
https://issues.apache.org/jira/browse/HADOOP-6507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White resolved HADOOP-6507.
---
Hadoop Flags: [Reviewed]
Resolution: Fixed
I've just committed this. Thanks Corinne!
Hadoop
On Mon, Apr 12, 2010 at 4:14 PM, Allen Wittenauer
awittena...@linkedin.com wrote:
So, does this mean that everything that has been committed for 0.22 is
actually going to be in 0.21? For example, symlinks were committed to trunk
for 0.22 according to JIRA.
Yes. Note that symlinks to date
Issue Type: Improvement
Reporter: Tom White
Such a feature would be useful to enforce MAPREDUCE-1637. It might also be
useful for users who wish to check their programs don't use Evolving APIs.
It could be implemented using an annotation processor:
http://java.sun.com
: Improvement
Components: documentation
Reporter: Tom White
Assignee: Tom White
Mark private implementation classes with the InterfaceAudience.Private or
InterfaceAudience.LimitedPrivate annotation to exclude them from user Javadoc
and JDiff.
--
This message
On Fri, Mar 26, 2010 at 11:43 AM, Owen O'Malley omal...@apache.org wrote:
On Mar 24, 2010, at 4:25 PM, Tom White wrote:
I agree that getting the release process restarted is of utmost
importance to the project. To help make that happen I'm happy to
volunteer to be a release manager
1 - 100 of 121 matches
Mail list logo
