To use maven for hadoop common builds
-
Key: HADOOP-6671
URL: https://issues.apache.org/jira/browse/HADOOP-6671
Project: Hadoop Common
Issue Type: Improvement
Components: build
Affects
Our org (Trend Micro) will be using an internal build based on 0.20 for at
least the rest of this year. It is, really, already 1.0 from our point of
view, the first ASF Hadoop release officially adopted into our production
environment. I hope other users of Hadoop will speak up on this thread
Chris K Wensel wrote:
are we saying we will de-deprecate the stable APIs in .20, or make the new APIs
introduced in .20 stable?
+1 on removing the deprecations on the stable APIs.
Yes. I too am +1 on removing deprecations in stable, public APIs in a
1.0 release. Code that uses only public
Todd Lipcon wrote:
With HDFS-200 we'd also need HDFS-142
Good to know. I' have to admit to being puzzled by HDFS-200, since
Nicholas resolved it as a duplicate on 7 January, yet Dhruba's continued
to post patches to it.
Dhruba, Stack: do you have any thoughts on the appropriateness of
nightly builds have incorrect VersionInfo
-
Key: HADOOP-6673
URL: https://issues.apache.org/jira/browse/HADOOP-6673
Project: Hadoop Common
Issue Type: Bug
Components: build
Hi Guys,
To throw in my 2 cents: it would be really nice to get out a 1.0 branch
based off of 0.20 it¹s not perfect, but releases never are. That¹s why you
can make more of them. :)
In terms of the significance of the 1.0 labeling, I think it's important for
adoption. I was telling someone at
LOL, I want a v100! :)
On 4/1/10 2:31 PM, Allen Wittenauer awittena...@linkedin.com wrote:
On 4/1/10 2:15 PM, Mattmann, Chris A (388J)
chris.a.mattm...@jpl.nasa.gov wrote:
In terms of the significance of the 1.0 labeling, I think it's important for
adoption.
Companies wanting a 1.0
I would like call for a vote to created a development branch of common
trunk to work on mavenizing hadoop common.
-Giri
Hi Guys,
To throw in my 2 cents: it would be really nice to get out a 1.0 branch
based off of 0.20 it¹s not perfect, but releases never are. That¹s why you
can make more of them. :)
In terms of the significance of the 1.0 labeling, I think it's important for
adoption. I was telling someone at
Performance Improvement in Secure RPC
-
Key: HADOOP-6674
URL: https://issues.apache.org/jira/browse/HADOOP-6674
Project: Hadoop Common
Issue Type: Improvement
Reporter: Jitendra Nath Pandey
+1 -C
On Thursday, April 1, 2010, Giridharan Kesavan gkesa...@apache.org wrote:
I would like call for a vote to created a development branch of common
trunk to work on mavenizing hadoop common.
-Giri
We have been testing the HDFS append code for 0.20 (using HDFS-200,
HDFS-142), but I believe it is not ready for production yet. I am guessing
that there would be another two months of testing before I would classify
0.20.3 + HDFS-200 as production quality. HDFS-200 touches code paths that
would
+1 for exploring. HBase TRUNK is now mavenized. Has kinks still but
its getting there. Will see if can get some of the experts hanging
in hbase space to help out with this effort.
St.Ack
On Thu, Apr 1, 2010 at 7:34 PM, Chris Douglas cdoug...@apache.org wrote:
+1 -C
On Thursday, April 1,
On Apr 1, 2010, at 10:50 AM, Doug Cutting wrote:
If it takes months, it is a failure. It should take weeks, if that.
On Apr 1, 2010, at 9:31 PM, Dhruba Borthakur wrote:
We have been testing the HDFS append code for 0.20 (using HDFS-200,
HDFS-142), but I believe it is not ready for
14 matches
Mail list logo
