Then that's may be a possible path to go... identify all prior art (what
Google cannot indeed claim) and make it public on the Hadoop/HBase pages so
that companies can feel confident taking the Hadoop/HBase root... Basically
*publicly* invalidate this patent with all reasonable arguments :-)
Typically if the system design is "what a person skilled in the art" would
have produced, this is NOT an invention...
----- Original Message -----
From: "Bruce Williams" <williams.br...@gmail.com>
To: <hbase-dev@hadoop.apache.org>
Sent: Thursday, January 21, 2010 12:53 PM
Subject: Re: Google patent over Map Reduce - Hbase reflections
The fact is Hadoop was modeled after the particular system design
Google developed from the start. So it is what it is. I don't think
you can "differentiate" that situation away.
Can Google patent MapReduce, which is basic CS and part of Lisp from
the 60's? That is what is interesting about this.
Bruce
On Thu, Jan 21, 2010 at 3:33 AM, Laurence Hubert
<laurence.hub...@free.fr> wrote:
Dear all,
I think the impact of this patent should not be underestimated. If
Hadoop/HBase is only an educational system and not used by anybody for any
business then I agree there is no threat to the community...
but if companies are relaying on it to do business (and some started to
evaluate the use of Hadoop/HBase in commercial systems) then the companies
businesses or products might be threatened. This means, unless something
is
done, companies cannot select Hadoop/HBase anymore for implementations
because this is too much of a risk... which is in fact the biggest threat
to
hadoop... it was becoming popular and companies started to consider
supporting it (providing development resources...) because this was a
possible platform for their businesses...
In my opinion a healthy attitude to this would be to analyse what was
actually *really* protected and be creative on how hadoop could/should
differentiate. Because if hadoop is just a 1:1 replica of the Google
system,
then there is no chance that it will attract more than the academic
community and its nice success story is going to end here... I see enough
intellectual power in the team to be able to take the Google patent and
produce the next generation...
My two cents,
Laurence Hubert
----- Original Message ----- From: "Kay Kay" <kaykay.uni...@gmail.com>
To: <hbase-dev@hadoop.apache.org>
Sent: Thursday, January 21, 2010 3:28 AM
Subject: Re: Google patent over Map Reduce - Hbase reflections
On 1/20/10 3:44 PM, stack wrote:
I've been following the thread. I would tend to side with the general
tenor
that has it that its likely a just-in-case move by Google and that the
likelihood of a Google suing Apache is not likely to happen in this
dimension.
That was my general idea as well.
Are you (or your employer) spooked Kay Kay?
Not at all - but just started this to see what the opinions of the
community might be w.r.t. this.
St.Ack
On Wed, Jan 20, 2010 at 3:34 PM, Kay Kay<kaykay.uni...@gmail.com> wrote:
A big thread currently going on at the hadoop common user mailing
list -
http://mail-archives.apache.org/mod_mbox/hadoop-common-user/201001.mbox/<
2c36b701001200817g77f245b1x6ba9d7d2cfd9e...@mail.gmail.com> .
A good number of you might have already seen that thread, but just
opening
up a thread for discussion to see what the thoughts of the community
are
,
w.r.t. patent and how much (if at all) of the application would be
related
to that / any refactorings as necessary as seen by the team or thoughts
in
general to the same.
--------------------------------------------------------------------------------
Ce message entrant est certifié sans virus connu.
Analyse effectuée par AVG - www.avg.fr
Version: 9.0.730 / Base de données virale: 271.1.1/2635 - Date: 01/20/10
20:18:00
--
“Discovering...discovering...we will never cease discovering...
and the end of all our discovering will be
to return to the place where we began
and to know it for the first time.”
-T.S. Eliot
--------------------------------------------------------------------------------
Ce message entrant est certifié sans virus connu.
Analyse effectuée par AVG - www.avg.fr
Version: 9.0.730 / Base de données virale: 271.1.1/2635 - Date: 01/20/10
20:18:00
