XQuery Function Documentation
http://exist-db.org/xquery/lucene
java:org.exist.xquery.modules.lucene.LuceneModule
A module for full text indexed searching based on Lucene.
ft:close
Close the current Lucene document and flush it to disk. Subsequent calls to ft:index will write to a new Lucene document.
- Returns:
- empty() :
ft:get-field
Retrieve the stored content of a field.
- Parameters:
-
$path* URI paths of documents or collections in database. Collection URIs should end on a '/'. $field query string - Returns:
- xs:string* : All documents that are match by the query
ft:has-index
Check if the given document has a lucene index defined on it. This method will return true for both, indexes created via collection.xconf or manual index fields added to the document with ft:index.
- Parameters:
-
$path Full path to the resource to check - Returns:
- xs:boolean* :
ft:index
Index an arbitrary chunk of (non-XML) data with Lucene. Syntax is inspired by Solr.
- Parameters:
-
$documentPath URI path of document in database. $solrExression XML syntax expected by Solr's add expression. Element should be called 'doc', e.g.<doc> <field name="field1">data1</field> <field name="field2" boost="value">data2</field> </doc> - Returns:
- empty() :
ft:index
Index an arbitrary chunk of (non-XML) data with Lucene. Syntax is inspired by Solr.
- Parameters:
-
$documentPath URI path of document in database. $solrExression XML syntax expected by Solr's add expression. Element should be called 'doc', e.g.<doc> <field name="field1">data1</field> <field name="field2" boost="value">data2</field> </doc> $close If true, close the Lucene document. Subsequent calls to ft:index will thus add to a new Lucene document. If false, the document remains open and is not flushed to disk. Call the ft:close function to explicitely close and flush the current document. - Returns:
- empty() :
ft:optimize
Calls Lucene's optimize method to merge all index segments into a single one. This is a costly operation and should not be used except for data sets which can be expected to remain unchanged for a while. The optimize will block the index for other write operations and may take some time. You need to be a user in group dba to call this function.
- Returns:
- empty() :
ft:query
Queries a node set using a Lucene full text index; a lucene index must already be defined on the nodes, because if no index is available on a node, nothing will be found. Indexes on descendant nodes are not used. The context of the Lucene query is determined by the given input node set. The query is specified either as a query string based on Lucene's default query syntax or as an XML fragment. See http://exist-db.org/lucene.html#N1029E for complete documentation.
- Parameters:
-
$nodes* The node set to search using a Lucene full text index which is defined on those nodes $query The query to search for, provided either as a string or text in Lucene's default query syntax or as an XML fragment to bypass Lucene's default query parser - Returns:
- node()* : all nodes from the input node set matching the query. match highlighting information will be available for all returned nodes. Lucene's match score can be retrieved via the ft:score function.
ft:query
Queries a node set using a Lucene full text index; a lucene index must already be defined on the nodes, because if no index is available on a node, nothing will be found. Indexes on descendant nodes are not used. The context of the Lucene query is determined by the given input node set. The query is specified either as a query string based on Lucene's default query syntax or as an XML fragment. See http://exist-db.org/lucene.html#N1029E for complete documentation.
- Parameters:
-
$nodes* The node set to search using a Lucene full text index which is defined on those nodes $query The query to search for, provided either as a string or text in Lucene's default query syntax or as an XML fragment to bypass Lucene's default query parser $options? An XML fragment containing options to be passed to Lucene's query parser. The following options are supported (a description can be found in the docs): <options> <default-operator>and|or</default-operator> <phrase-slop>number</phrase-slop> <leading-wildcard>yes|no</leading-wildcard> <filter-rewrite>yes|no</filter-rewrite> </options> - Returns:
- node()* : all nodes from the input node set matching the query. match highlighting information will be available for all returned nodes. Lucene's match score can be retrieved via the ft:score function.
ft:query-field
Queries a Lucene field, which has to be explicitely created in the index configuration.
- Parameters:
-
$field* The lucene field name. $query The query to search for, provided either as a string or text in Lucene's default query syntax or as an XML fragment to bypass Lucene's default query parser - Returns:
- node()* : all nodes from the input node set matching the query. match highlighting information will be available for all returned nodes. Lucene's match score can be retrieved via the ft:score function.
ft:query-field
Queries a Lucene field, which has to be explicitely created in the index configuration.
- Parameters:
-
$field* The lucene field name. $query The query to search for, provided either as a string or text in Lucene's default query syntax or as an XML fragment to bypass Lucene's default query parser $options? An XML fragment containing options to be passed to Lucene's query parser. The following options are supported (a description can be found in the docs): <options> <default-operator>and|or</default-operator> <phrase-slop>number</phrase-slop> <leading-wildcard>yes|no</leading-wildcard> <filter-rewrite>yes|no</filter-rewrite> </options> - Returns:
- node()* : all nodes from the input node set matching the query. match highlighting information will be available for all returned nodes. Lucene's match score can be retrieved via the ft:score function.
ft:remove-index
Remove any (non-XML) Lucene index associated with the document identified by the path parameter. This function will only remove indexes which were manually created by the user via the ft:index function. Indexes defined in collection.xconf will NOT be removed. They are maintained automatically by the database. Please note that non-XML indexes will also be removed automatically if the associated document is deleted.
- Parameters:
-
$documentPath URI path of document in database. - Returns:
- empty() :
ft:score
Returns a computed relevance score for the given node. The score is the sum of all relevance scores provided by Lucene for the node and its descendants. In general, the score will be a number between 0.0 and 1.0 if the query had $node as context. If the query targeted multiple descendants of $node (e.g. 'title' and 'author' within a 'book'), the score will be the sum of all sub-scores and may thus be greater than 1.
- Parameters:
-
$node the context node - Returns:
- xs:float* : sum of all relevance scores provided by Lucene for all matches below the given context node
ft:search
Search for (non-XML) data with lucene
- Parameters:
-
$path* URI paths of documents or collections in database. Collection URIs should end on a '/'. $query query string - Returns:
- node() : All documents that are match by the query
ft:search
Search for (non-XML) data with lucene
- Parameters:
-
$query query string - Returns:
- node() : All documents that are match by the query