Save This Page
Home » nutch-1.0 » org.apache.nutch » segment » [javadoc | source]
org.apache.nutch.segment
public class: SegmentMerger [javadoc | source]
java.lang.Object
   org.apache.hadoop.conf.Configured
      org.apache.nutch.segment.SegmentMerger

All Implemented Interfaces:
    org.apache.hadoop.mapred.Mapper, org.apache.hadoop.mapred.Reducer

This tool takes several segments and merges their data together. Only the latest versions of data is retained.

Optionally, you can apply current URLFilters to remove prohibited URL-s.

Also, it's possible to slice the resulting segment into chunks of fixed size.

Important Notes

Which parts are merged?

It doesn't make sense to merge data from segments, which are at different stages of processing (e.g. one unfetched segment, one fetched but not parsed, and one fetched and parsed). Therefore, prior to merging, the tool will determine the lowest common set of input data, and only this data will be merged. This may have some unintended consequences: e.g. if majority of input segments are fetched and parsed, but one of them is unfetched, the tool will fall back to just merging fetchlists, and it will skip all other data from all segments.

Merging fetchlists

Merging segments, which contain just fetchlists (i.e. prior to fetching) is not recommended, because this tool (unlike the org.apache.nutch.crawl.Generator doesn't ensure that fetchlist parts for each map task are disjoint.

Duplicate content

Merging segments removes older content whenever possible (see below). However, this is NOT the same as de-duplication, which in addition removes identical content found at different URL-s. In other words, running DeleteDuplicates is still necessary.

For some types of data (especially ParseText) it's not possible to determine which version is really older. Therefore the tool always uses segment names as timestamps, for all types of input data. Segment names are compared in forward lexicographic order (0-9a-zA-Z), and data from segments with "higher" names will prevail. It follows then that it is extremely important that segments be named in an increasing lexicographic order as their creation time increases.

Merging and indexes

Merged segment gets a different name. Since Indexer embeds segment names in indexes, any indexes originally created for the input segments will NOT work with the merged segment. Newly created merged segment(s) need to be indexed afresh. This tool doesn't use existing indexes in any way, so if you plan to merge segments you don't have to index them prior to merging.
Nested Class Summary:
public static class  SegmentMerger.ObjectInputFormat  Wraps inputs in an {@link MetaWrapper}, to permit merging different types in reduce and use additional metadata. 
public static class  SegmentMerger.SegmentOutputFormat   
Constructor:
 public SegmentMerger() 
 public SegmentMerger(Configuration conf) 
Method from org.apache.nutch.segment.SegmentMerger Summary:
close,   configure,   main,   map,   merge,   reduce,   setConf
Methods from java.lang.Object:
equals,   getClass,   hashCode,   notify,   notifyAll,   toString,   wait,   wait,   wait
Method from org.apache.nutch.segment.SegmentMerger Detail:
 public  void close() throws IOException 
 public  void configure(JobConf conf) 
 public static  void main(String[] args) throws Exception 
 public  void map(Text key,
    MetaWrapper value,
    OutputCollector output,
    Reporter reporter) throws IOException 
 public  void merge(Path out,
    Path[] segs,
    boolean filter,
    boolean normalize,
    long slice) throws Exception 
 public  void reduce(Text key,
    Iterator values,
    OutputCollector output,
    Reporter reporter) throws IOException 
    NOTE: in selecting the latest version we rely exclusively on the segment name (not all segment data contain time information). Therefore it is extremely important that segments be named in an increasing lexicographic order as their creation time increases.
 public  void setConf(Configuration conf)