Skip to main content
An enhancement has been made to execute some processing on large objects at extraction time rather than by the cube during query time. This is particularly important for the processing of the Vectors. The interface IDeeTaskExtractionProcedure defines the contract:
The definition introduces the tags:
  1. extractionProcedure, which defines the pre-processing to apply on the data retrieved from the MDX query before generating the result
  2. extractionProcedureValue, a tag to access data generated by the extraction procedure

JSON format

This is an example of an extraction procedure that allows computing a large number of percentiles for a measure returning an IVector.
In the previous example, a file was still being generated; this is the default behaviour. It is possible to change this behaviour and keep the data in memory for further processing. This can be useful when writing custom code and deciding to do something else with the data. The API is using the following interfaces:
  • IMemoryOutputHandler, interface for the output handler keeping data in memory. A default SimpleMemoryOutputHandler is provided to keep the content of the row data.
  • IMemoryDeeTaskResultInfo, interface for a bean holding DEE memory result information. A default SimpleMemoryDeeTaskResultInfo gives access to the data object.
The memory output handler can only be created by code using the InMemoryDeeOutput class. In this case, the goal is to just fill a Map with the results without caring about the locations.