Arun,
Awesome, thanks for working on this. I'll definitely kick the tires.
Noticed the mvn version is 2.0.0-alpha, should we make it 2.0.0-alpha1
in case we need to roll multiple alpha releases?
Thanks,
Eli
On Wed, May 9, 2012 at 9:58 AM, Arun C Murthy a...@hortonworks.com wrote:
I've created
-1 (nonbinding), we are currently facing a minicluster semantic change
of some kind, or more than one:
https://issues.apache.org/jira/browse/HBASE-5966
There are other HBase JIRAs related to 2.0.0-alpha that we are working
on, but I'd claim those are all our fault for breaking abstractions
+1 I downloaded it and run a few simple tests wordcount etc. on a single node
cluster with no security.
--Bobby Evans
On 5/9/12 11:58 AM, Arun C Murthy a...@hortonworks.com wrote:
I've created a release candidate for hadoop-2.0.0-alpha that I would like to
release.
It is available at:
On May 9, 2012, at 10:05 AM, Eli Collins wrote:
Arun,
Awesome, thanks for working on this. I'll definitely kick the tires.
Noticed the mvn version is 2.0.0-alpha, should we make it 2.0.0-alpha1
in case we need to roll multiple alpha releases?
I was thinking 2.0.1-alpha, or
Sounds good Arun.
How should we consider the suitability and stability of MiniMRCluster
for downstream projects?
On Wed, May 9, 2012 at 11:30 AM, Arun C Murthy a...@hortonworks.com wrote:
No worries Andy. I can spin an rc1 once we can pin-point the bug.
thanks,
Arun
On May 9, 2012, at
For this reason, in HDFS, we change MiniDFSCluster to LimitedPrivate and
not treat it as such:
@InterfaceAudience.LimitedPrivate({HBase, HDFS, Hive, MapReduce,
Pig})
@InterfaceStability.Unstable
public class MiniDFSCluster { ...}
On Wed, May 9, 2012 at 11:33 AM, Andrew Purtell
+1 (non-binding)
Downloaded the tarball and ran example mr jobs on a single node
cluster, also tried distributed shell jobs.
Best Regards
Ahmed
On Wed, May 9, 2012 at 9:58 AM, Arun C Murthy a...@hortonworks.com wrote:
I've created a release candidate for hadoop-2.0.0-alpha that I would like to
Folks,
In the release numbering discussions that we had less than 3 months ago, there
was a suggestion about 0.22 release being an active release, and that it should
be reserved a major release number, since it has major changes (especially in
HDFS, since a viable HA based on a working standby
Hi Suresh,
The unstable designation makes sense. As would one for MiniMRCluster.
I was over the top initially to surprise. I'm sure the MR minicluster seems a
minor detail.
Maybe it's worth thinking about the miniclusters differently? Please pardon if
I am rehashing an old discussion.
Hi Andrew,
Have you seen the new MiniMRClientCluster class? It's meant to be what
you describe - a minicluster which only exposes external APIs --
most importantly a way of getting at a JobClient to submit jobs. We
have it implemented in both 1.x and 2.x at this point, though I don't
recall if
On Wed, May 9, 2012 at 11:28 AM, Arun C Murthy a...@hortonworks.com wrote:
On May 9, 2012, at 10:05 AM, Eli Collins wrote:
Arun,
Awesome, thanks for working on this. I'll definitely kick the tires.
Noticed the mvn version is 2.0.0-alpha, should we make it 2.0.0-alpha1
in case we need to
11 matches
Mail list logo
