The Query Executor application is intended take an AspireObject containing a query, submit it to a Search Engine and load the results from the engine back in to the AspireObject.
This application receives a job containing a query and concatenates all the top level document elements together in name value pairs to form a parameter list for a URL. The location of the URL is constructed by concatenating the configured server and (if specified) the request path. The the request path is not specified, the application looks for a value in the document /doc/aspireHttpFeederServlet/@fullPath attribute (which is populated by applications such as the FAST Query Listener, which use the HTTP Feeder component).
The application then uses the Fetch URL component to submit the query to the search engine and the XML Loader or Text Loader component as appropriate to load the results from that query. XML results will be loaded directly in to the root of the AspireObject (so a result set that has <SEGMENTS> as it's root will appear as /doc/SEGMENTS). Results which are not XML will be loaded (as a string) in to the element specified in the configuration.
The application can also be forced to skip query execution by the presence of a tag in the input document. This is useful if this application is chained after another application (such as the Federation Dispatcher) that may have performed the query.
See also the Fetch URL, XML Loader and Text Loader components