I have updated
https://issues.apache.org/jira/browse/HADOOP-7391
with a html file that is for adding as an overview.html to the
classification package.
The text is mostly what was in HADOOP-5073; i have added 3 FAQs.
No offense taken.
Sanjay and I chatted offline. We disagree on whether Private should be
scoped to the whole project (Hadoop), or to subprojects (Common, HDFS,
MapReduce). The intent of HADOOP-5073 was for the latter, but I'm not
convinced it buys us anything really, which is why I've been
On Jun 9, 2011, at 10:27 AM, Tom White wrote:
Looking at current usage in Hadoop, there are only 4 LimitedPrivate
references to HBase (the http, io.retry, ipc, and metrics packages in
Common), and 2 references to Pig (the two LineRecordReader classes in
MapReduce). The other LimitedPrivate
On 06/09/2011 08:23 PM, Stack wrote:
Nice reality check and thanks for the how it was addressed elsewhere Steve.
As you say, it sounds like a large undertaking but it would be a sweet
service for the downstreamers.
as an aside, the thing that usually prevents you using Java apps as
libraries
projects that are
closely tied to Hadoop as projects eligible for LimitedPrivate.
{HBase, HDFS, Hive, MapReduce, Pig}. This list could grow in the
future.
I'm going to talk about my experience on the Ant team.
One of the lessons of that project is that in the open source world, you
can't predict
Looking at current usage in Hadoop, there are only 4 LimitedPrivate
references to HBase (the http, io.retry, ipc, and metrics packages in
Common), and 2 references to Pig (the two LineRecordReader classes in
MapReduce). The other LimitedPrivate references are all to HDFS or
MapReduce. Given
AM, Tom White tom.e.wh...@gmail.com wrote:
Looking at current usage in Hadoop, there are only 4 LimitedPrivate
references to HBase (the http, io.retry, ipc, and metrics packages in
Common), and 2 references to Pig (the two LineRecordReader classes in
MapReduce). The other LimitedPrivate
usage in Hadoop, there are only 4 LimitedPrivate
references to HBase (the http, io.retry, ipc, and metrics packages in
Common), and 2 references to Pig (the two LineRecordReader classes in
MapReduce). The other LimitedPrivate references are all to HDFS or
MapReduce. Given that Private means
On Mon, Jun 6, 2011 at 1:45 PM, Allen Wittenauer a...@apache.org wrote:
On Jun 6, 2011, at 11:34 AM, Stack wrote:
On Mon, Jun 6, 2011 at 9:45 AM, Allen Wittenauer a...@apache.org wrote:
I have some concerns over the recent usage of LimitedPrivate being
opened up to HBase.
to Hadoop as projects eligible for LimitedPrivate.
{HBase, HDFS, Hive, MapReduce, Pig}. This list could grow in the
future.
I'm going to talk about my experience on the Ant team.
One of the lessons of that project is that in the open source world, you
can't predict how your code gets used
comes with a cost. That is what we are avoiding with
LimitedPrivate. The intention was to include the following projects
that are
closely tied to Hadoop as projects eligible for LimitedPrivate.
{HBase, HDFS, Hive, MapReduce, Pig}. This list could grow in
the
future.
I'm going to talk about my
: Monday, June 06, 2011 9:33 PM
To: general@hadoop.apache.org
Subject: Re: LimitedPrivate and HBase
On Jun 6, 2011, at 6:23 PM, Todd Lipcon wrote:
Nah, I just think these meta discussions waste an awful lot of time
that's better spent making real progress on the code, or reviewing the
complex
From: Allen Wittenauer a...@apache.org
OK. That's make it easier to just
-1 changes like this with reasoning such as HBase is not a
related project. Then we can go back working on core
Hadoop.
Seriously?
Forget what I said about filing a JIRA (and working on it) to give HttpServer
an
something be marked LimitedPrivate to HBase instead of just making it Public
and being done with it?
was to include the following projects that
are
closely tied to Hadoop as projects eligible for LimitedPrivate.
{HBase, HDFS, Hive, MapReduce, Pig}. This list could grow in the
future.
When such projects break because of API change, we can co-ordinate as
community and fix the issues
that
are
closely tied to Hadoop as projects eligible for LimitedPrivate.
{HBase, HDFS, Hive, MapReduce, Pig}. This list could grow in the
future.
When such projects break because of API change, we can co-ordinate as
community and fix the issues. This is not true for some application that we
do not know
public comes with a cost. That is what we are avoiding with
LimitedPrivate. The intention was to include the following projects that
are
closely tied to Hadoop as projects eligible for LimitedPrivate.
{HBase, HDFS, Hive, MapReduce, Pig}. This list could grow in the
future.
When such projects
On 06/06/2011 05:45 PM, Allen Wittenauer wrote:
I have some concerns over the recent usage of LimitedPrivate being
opened up to HBase. Shouldn't HBase really be sticking to public APIs rather
than poking through some holes? If HBase needs an API, wouldn't other clients
as well?
Not really. It isn't part of any Hadoop release. And no official Hadoop
release will run hbase reliably.
On Tue, Jun 7, 2011 at 2:09 AM, Steve Loughran ste...@apache.org wrote:
On 06/06/2011 05:45 PM, Allen Wittenauer wrote:
I have some concerns over the recent usage of
I have some concerns over the recent usage of LimitedPrivate being
opened up to HBase. Shouldn't HBase really be sticking to public APIs rather
than poking through some holes? If HBase needs an API, wouldn't other clients
as well?
other clients as well?
IMO LimitedPrivate can be used to open an API for a specific project when
it's not clear that the API is generally useful, and/or we anticipate the
API might be pretty unstable. Marking it LimitedPrivate to HBase gives us
the opportunity to talk to the HBase team and say hey
through some holes? If HBase needs an API, wouldn't
other clients as well?
IMO LimitedPrivate can be used to open an API for a specific project when
it's not clear that the API is generally useful, and/or we anticipate the
API might be pretty unstable. Marking it LimitedPrivate to HBase gives
On Jun 6, 2011, at 11:34 AM, Stack wrote:
On Mon, Jun 6, 2011 at 9:45 AM, Allen Wittenauer a...@apache.org wrote:
I have some concerns over the recent usage of LimitedPrivate being
opened up to HBase. Shouldn't HBase really be sticking to public APIs
rather than poking through
On Jun 6, 2011, at 4:22 PM, Andrew Purtell wrote:
Perhaps opening a jira for a cleaner framework for HttpServer extension could
be useful?
Sure. That's probably what should have happened to begin with rather
than the quickly changing the API to a different classification. I was a
On Mon, Jun 6, 2011 at 6:05 PM, Allen Wittenauer a...@apache.org wrote:
On Jun 6, 2011, at 5:56 PM, Todd Lipcon wrote:
Or because this is the sort of thing that could take weeks of discussion
or
just 5 minutes to unblock HBase from moving on to trunk. I'd rather have
the
weeks of
On Jun 6, 2011, at 6:08 PM, Todd Lipcon wrote:
Let's face it: this happened because it was HBase. If it was almost
anyone else, it would have sat there and *that's* the point where I'm
mainly concerned.
If you want to feel better, take a look at HDFS-941, HDFS-347, and
26 matches
Mail list logo
