hadoop-common-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Hadoop Wiki] Trivial Update of "BristolHadoopWorkshop" by SteveLoughran
Date Fri, 16 Oct 2009 16:11:29 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change notification.

The "BristolHadoopWorkshop" page has been changed by SteveLoughran:
http://wiki.apache.org/hadoop/BristolHadoopWorkshop?action=diff&rev1=15&rev2=16

  
   1. WS-* : the big, comfortable, safe long-haul option, the Airbus A380. You, the passenger,
get looked after by the cabin crew.
  
-  1. The floatplane. Agile, can get around fast, but you read the location of the life vest
instructions very carefully, make a note of the exit in the roof and hope that you aren't
the one who has to get on the float to dock the plane with the boat. It isn't quite as comfy
as the big plane, but it is easier to get up and around with it. 
+  1. The floatplane. Agile, can get around fast, but you read the location of the life vest
instructions very carefully, make a note of the exit in the roof and hope that you aren't
the one who has to get on the float to dock the plane with the boat. It isn't quite as comfy
as the big plane, but it is easier to get up and around with it.
  
  Two RESTful world views were discussed
  
@@ -225, +225 @@

  
  There was discussion on handing big graphs in the system, ones where the graph itself is
very large. Someone need's to take Paolo's PageRank-over-MapReduce code and test it on bigger
data sets.
  
- There was a good point on what is "efficient" in this world. 
+ There was a good point on what is "efficient" in this world.
  
  Yes, something done as a chain of MR jobs on a Hadoop cluster may seem an inefficient approach,
but if there is no other way to store that much data, or run through it, then graph people
will be happy.
  
@@ -233, +233 @@

  
  This was a discussion topic run by Julio
  
- * 400 Y! staff are moving to MS. How many are search specialists, versus Hadoop hackers.
+  * 400 Y! staff are moving to MS. How many are search specialists, versus Hadoop hackers.
- 
- * Y! is driving large scale tests, facebook is #2.
+  * Y! is driving large scale tests, facebook is #2.
- * Y! are making Hadoop the core of the company; it is their LOB of datacentre.
+  * Y! are making Hadoop the core of the company; it is their LOB of datacentre.
  
  What are the risks of the Merger, and warning signs of trouble:
   1.  silence: Y! developers do their own fork, it goes closed source. We have seen this
happen in other OSS projects (Axis), where a single company suddenly disappears. There is
no defence from this other than making sure development knowledge is widespread. The JIRA-based
discussion/documentation is good here,

Mime
View raw message