Define Java Aggregation Processors

1. Under Aggregation processors, click Add processor.
2. In the Add processor dialog box, select Java, give a name to the processor, and then choose one of the following default processors.

   Aggregation Processor	Description
   Basic Aggregation Processor	Class Id: com.exalead.cloudview.consolidation.processors.java.classic. BasicAggregationProcessor Add/set metas, directives, or parts from documents at the end of paths, returned by the given graph matching expression. See the example below this table.
   Classification Processor	Class Id: com.exalead.cloudview.consolidation.processors.java.classic. ClassficationAggregationProcessor Generates classification metadata representing path nodes ('node1_id/node2_id/node3_id...')
   Discard Processor	Class Id: com.exalead.cloudview.consolidation.processors.java.classic. DiscardAggregationProcessor Discards documents matching the given document types. For a use case example, see UC-8: Consolidating Data from Storage Service.
   Set Directive Processor	Class Id: com.exalead.cloudview.consolidation.processors.java.classic. SetDirectiveAggregationProcessor Sets the given directive on the processed document.
   Set Meta Processor	Class Id: com.exalead.cloudview.consolidation.processors.java.classic. SetMetaAggregationProcessor Sets the given meta on the processed document.
   Storage Service Key Flattener Processor	Class Id: com.exalead.cloudview.consolidation.processors.java.classic. StorageServiceKeyFlattenerAggregationProcessor Sets metas on a document coming from the Storage Service. For a use case example, see UC-8: Consolidating Data from Storage Service.
   Interconnector Aggregator Processor	Class Id: com.exalead.cloudview.consolidation.processors.java. InterconnectorAggregatorProcessor Aggregates a parent document with its child document, given a graph path from parent to child. For a use case example, see Using the Interconnector Service in the Exalead CloudView Connectors Guide.

   For example, with the Basic Aggregation Processor, you can replace the following Groovy code, which rewrites metas at the end of paths:

   process("eno:bo:CATPart") {
   	for (node in match(it, "-eno:from[eno:co:Viewable].eno:to[eno:bo:CgrViewable].-eno:thumbnail")*.last()) {
   		it.metas."3dthb_46_phyid" += node.metas."physicalid";
   		it.metas."3dthb_46_name" += node.metas."sdc_46_3dthb_46_name";
   		it.metas."3dthb_46_format" += node.metas."sdc_46_3dthb_46_format";
   	}
   }

   By the following configuration:
   
   

3. Click Apply.

In Java, to define an Aggregation processor in the create/update action context, you need to implement the IJavaAllUpdatesAggregationProcessor interface. Here is the actual interface definition:

/**
 *  Defines the interface for all Java aggregation processors that need to perform document operations
 *  in a non-delete context.
 */
 public interface IJavaAllUpdatesAggregationProcessor extends IJavaAggregationProcessor {
   /**
   * Performs the aggregation operations of the client's processor for the document transmitted, 
   * with the help of the handler provided.
   * 
   * @param handler The aggregation handler with the allowed operations for the processor.
   * @param document The reference document.
   * @throws Exception Occurs for whatever reason in the client's implementation. 
   * The exception will most likely be wrapped with contextual information before further propagation.
   */
   public void process(final IJavaAllUpdatesAggregationHandler handler, final IAggregationDocument document)
 throws Exception;
}

The parent interface is defined as follows:

/**
 * Defines the interface for all Java aggregation processors that need to 
 * perform document operations in a non-delete context.
 */
public interface IJavaAllUpdatesAggregationProcessor extends IJavaAggregationProcessor {
   /**
   * Performs the aggregation operations of the client's processor for the document transmitted, 
   * with the help of the handler provided.
   * 
   * @param handler The aggregation handler with the allowed operations for the processor.
   * @param document The reference document.
   * @throws Exception Occurs for whatever reason in the client's implementation. 
   * The exception will most likely be wrapped with contextual information before further propagation.
   */
    public void process(final IJavaAllUpdatesAggregationHandler handler, final IAggregationDocument document)
 throws Exception;
}

The class hierarchy is the following:

For the delete action context, you have to implement the IJavaDeleteAggregationProcessor interface as follows:

/**
 * Defines the interface for all Java aggregation processors that need to perform delete
 * processing on documents.
 */
public interface IJavaDeleteAggregationProcessor extends IJavaAggregationProcessor {
   /**
   * Performs the aggregation operations of the client's processor for the document transmitted, 
   * with the help of the handler provided.
   * 
   * @param handler The aggregation handler with the allowed operations for the processor.
   * @param document The reference document.
   * @throws Exception Occurs for whatever reason in the client's implementation. 
   * The exception will most likely be wrapped with contextual information before further propagation.
   */
   public void process(final IJavaDeleteAggregationHandler handler, final IAggregationDocument document)
 throws Exception;}

And finally, the class hierarchy is: