*
* Used to store useful data/metadata for post search processing.
* Will mostly be updated by the query builder. Keys should be named after the fetch function parameters,
* when applicable.
*
* Example : Knowing which subtress were used as filters allows
* for picking the right URL for a potentially multi-located
* search result.
*
* Example :
* <code>
* array( 'subtree_array' => array( 2, 43 ) );
* </code>
*
* @see ezfeZPSolrQueryBuilder::searchPluginInstance
* @var array
*/
public $postSearchProcessingData = array();
static $InstallationID;
static $SolrDocumentFieldName;
// @since ezfind 2.2, information
public static $fieldTypeContexts = array( 'search' => 'DatatypeMap', 'facet' => 'DatatypeMapFacet', 'sort' => 'DatatypeMapSort', 'filter' => 'DatatypeMapFilter' );
const PENDING_ACTION_INDEX_SUBTREE = 'index_subtree';
}
eZSolr::$SolrDocumentFieldName = new ezfSolrDocumentFieldName();
?>
