XML Configuration Reference : Search : SearchCommand
 
SearchCommand
com.exalead.mercury.mami.search.v20.SearchCommand
Search API command
Parent elements:
com.exalead.mercury.mami.search.v20.SearchAPIConfig (as SearchAPIConfig)
Attributes:
Name
Type
Default value
Description
defaultLogic
string
Default search logic (can be overriden using API parameters).
defaultTarget
string
Default search target (can be overriden using API parameters).
targetReporting
string
Target reporting to use for the search queries.
customRunnerFactoryClassId
string
maxConcurrentQueries
int
0
The maximum number of concurrent queries processed by the search server. If this limit is reached, incoming queries will be queued. 0 means the number of core of the search server times two.
maxWaitingQueries
int
200
When the maximum number of concurrent queries is reached the queries are put in a queue. This setting configures the maximum length of this queue. When this maximum is reached the query is rejected.
base
string
/search-api
HTTP path for this command
enableSOAP
boolean
isAliveSynchronous
boolean
True
Should the query be performed synchronously on isAlive call or should it run in a background thread, and cached result be returned.
isAliveAsynchronousDelayS
int
5
Elapsed time between two queries if the query is performed asynchronously.
Nested elements:
Name
Type
Description
customRunnerFactoryParams
exa.bee.KeyValue*
isAliveQueries
exa.bee.StringValue*
SearchCache
com.exalead.mercury.mami.search.v20.SearchCache*
List of caches for this search command. Cache entries will be looked up in all caches, in the order in which they are given. Incoming queries will be inserted in the first cache which accepts them. This allows complex configurations where you warmup some queries, and don't want them to be evicted by regular traffic

<TimeBasedSearchCache name="time" cacheQueries="false">
<WarmUpQuery args="q=#all" />
</TimeBasedSearchCache>
<ConsistentSearchCache name="default" />
<SearchCommand caches="time,default" />