Changes between Version 7 and Version 8 of PDAD_Applications

Timestamp:

Jan 14, 2010, 2:04:29 PM (14 years ago)

Author:

cristina.basescu

Comment:

--

PDAD_Applications

@@ -14 +14 @@
 == !MapReduce ==
 
-Making design choices for MapReduce is an intricate task. On the one hand, there are many decisions to be made, such as to have or not to have a Combiner (cuts down the amount of data transferred from the Mapper to the Reducer), a Partitioner (partitions the output of mappers per reducer), or even a CompressionCodec (compresses the intermediate outputs from mappers to reducers) or a Comparator to do a secondary sort before the reduce phase. On the other hand, complex combinations in specifying these extra features may lead to a too long development time, which is not worth it.
+Making design choices for !MapReduce is an intricate task. On the one hand, there are many decisions to be made, such as to have or not to have a Combiner (cuts down the amount of data transferred from the Mapper to the Reducer), a Partitioner (partitions the output of mappers per reducer), or even a !CompressionCodec (compresses the intermediate outputs from mappers to reducers) or a Comparator to do a secondary sort before the reduce phase. On the other hand, complex combinations in specifying these extra features may lead to a too long development time, which is not worth it.
   
 TODO Claudiu for his apps
@@ -20 +20 @@
 == Pig ==
 
-On the contrary to MapReduce, writing code in PigLatin is as straight forward as it can be 
+On the contrary to !MapReduce, writing code in !PigLatin is as straight forward as it can be 
 TODO Claudiu for his apps