Java Lucene et Zend_Search_Lucene fournissent des langages de requêtes plutôt puissants. Ces langages sont pratiquement pareils, exceptées les quelques différences ci-dessous. La syntaxe complète du langage de requêtes Java Lucene peut être trouvée ici. Une requête est décomposée en termes et opérateurs. Il y a 3 types de termes : le termes simples, les phrases et les sous-requêtes. Un terme simple est un simple mot, tel que "test" ou "hello". Une phrase est un groupe de mots inclus dans des double guillemets, tel que "hello dolly". Une sous-requête est une requête incluse dans des parenthèses, tel que "(hello dolly)". De multiples termes peuvent être combinés ensemble avec des opérateurs booléens pour former des requêtes complexes (voyez ci-dessous). Lucene supporte les champs de données. Lorsque vous effectuez une recherche, vous pouvez soit spécifier un champ, soit utiliser le champ par défaut. Le nom du champ dépend des données indexées et le champ par défaut est défini par les paramètres courants. La première différence et la plus significative avec Java Lucene est que par défaut les termes sont cherchés dans tous les champs. Il y a deux méthodes statiques dans la classe Zend_Search_Lucene qui permettent au développeur de configurer ces paramètres : La valeur NULL indique que la recherche est effectuée dans tous les champs. C'est le paramétrage par défaut Vous pouvez chercher dans des champs spécifiques en tapant le nom du champ suivi de ":", suivi du terme que vous cherchez. Par exemple, prenons un index Lucene contenant deux champs -title et text- avec text comme champ par défaut. Si vous voulez trouver le document ayant pour titre "The Right Way" qui contient le text "don't go this way", vous pouvez entrer : or "text" étant le champ par défaut, l'indicateur de champ n'est pas requis. Note: Le champ n'est valable que pour le terme, la phrase ou la sous-requête qu'il précède directement, ainsi la requête ne trouvera que "Do" dans le champ 'title'. Elle trouvera "it" et "right" dans le champ par défaut (si le champ par défaut est défini) ou dans tous les champs indexés (si le champ par défaut est défini à NULL). Lucene supporte les recherches avec joker sur un ou plusieurs caractères au sein des termes simples (mais pas dans les phrases). Pour effectuez une recherche avec joker sur un seul caractère, utilisez le symbole "?". Pour effectuez une recherche avec joker sur plusieurs caractères, utilisez le symbole "*". La recherche avec un joker sur un seul caractère va faire correspondre le terme avec le "?" remplacé par n'importe quel autre caractère unique. Par exemple, pour trouver "text" ou "test" vous pouvez utiliser la recherche : Multiple character wildcard searches look for 0 or more characters when matching strings against terms. For example, to search for test, tests or tester, you can use the search: You can use "?", "*" or both at any place of the term: It searches for "write", "wrote", "written", "rewrite", "rewrote" and so on. Starting from ZF 1.7.7 wildcard patterns need some non-wildcard prefix. Default prefix length is 3 (like in Java Lucene). So "*", "te?t", "*wr?t*" terms will cause an exception Please note, that it's not a Zend_Search_Lucene_Search_QueryParserException, but a Zend_Search_Lucene_Exception. It's thrown during query rewrite (execution) operation.. It can be altered using Zend_Search_Lucene_Search_Query_Wildcard::getMinPrefixLength() and Zend_Search_Lucene_Search_Query_Wildcard::setMinPrefixLength() methods. Lucene supports modifying query terms to provide a wide range of searching options. "~" modifier can be used to specify proximity search for phrases or fuzzy search for individual terms. Range queries allow the developer or user to match documents whose field(s) values are between the lower and upper bound specified by the range query. Range Queries can be inclusive or exclusive of the upper and lower bounds. Sorting is performed lexicographically. This will find documents whose mod_date fields have values between 20020101 and 20030101, inclusive. Note that Range Queries are not reserved for date fields. You could also use range queries with non-date fields: This will find all documents whose titles would be sorted between Aida and Carmen, but not including Aida and Carmen. Inclusive range queries are denoted by square brackets. Exclusive range queries are denoted by curly brackets. If field is not specified then Zend_Search_Lucene searches for specified interval through all fields by default. Zend_Search_Lucene as well as Java Lucene supports fuzzy searches based on the Levenshtein Distance, or Edit Distance algorithm. To do a fuzzy search use the tilde, "~", symbol at the end of a Single word Term. For example to search for a term similar in spelling to "roam" use the fuzzy search: This search will find terms like foam and roams. Additional (optional) parameter can specify the required similarity. The value is between 0 and 1, with a value closer to 1 only terms with a higher similarity will be matched. For example: The default that is used if the parameter is not given is 0.5. Wildcard, range and fuzzy search queries may match too many terms. It may cause incredible search performance downgrade. So Zend_Search_Lucene sets a limit of matching terms per query (subquery). This limit can be retrieved and set using Zend_Search_Lucene::getTermsPerQueryLimit()/Zend_Search_Lucene::setTermsPerQueryLimit($limit) methods. Default matched terms per query limit is 1024. Lucene supports finding words from a phrase that are within a specified word distance in a string. To do a proximity search use the tilde, "~", symbol at the end of the phrase. For example to search for a "Zend" and "Framework" within 10 words of each other in a document use the search: Java Lucene and Zend_Search_Lucene provide the relevance level of matching documents based on the terms found. To boost the relevance of a term use the caret, "^", symbol with a boost factor (a number) at the end of the term you are searching. The higher the boost factor, the more relevant the term will be. Boosting allows you to control the relevance of a document by boosting individual terms. For example, if you are searching for and you want the term "PHP" to be more relevant boost it using the ^ symbol along with the boost factor next to the term. You would type: This will make documents with the term PHP appear more relevant. You can also boost phrase terms and subqueries as in the example: By default, the boost factor is 1. Although the boost factor must be positive, it may be less than 1 (e.g. 0.2). Boolean operators allow terms to be combined through logic operators. Lucene supports AND, "+", OR, NOT and "-" as Boolean operators. Java Lucene requires boolean operators to be ALL CAPS. Zend_Search_Lucene does not. AND, OR, and NOT operators and "+", "-" defines two different styles to construct boolean queries. Unlike Java Lucene, Zend_Search_Lucene doesn't allow these two styles to be mixed. If the AND/OR/NOT style is used, then an AND or OR operator must be present between all query terms. Each term may also be preceded by NOT operator. The AND operator has higher precedence than the OR operator. This differs from Java Lucene behavior. The AND operator means that all terms in the "AND group" must match some part of the searched field(s). To search for documents that contain "PHP framework" and "Zend Framework" use the query: The OR operator divides the query into several optional terms. To search for documents that contain "PHP framework" or "Zend Framework" use the query: The NOT operator excludes documents that contain the term after NOT. But an "AND group" which contains only terms with the NOT operator gives an empty result set instead of a full set of indexed documents. To search for documents that contain "PHP framework" but not "Zend Framework" use the query: &&, ||, and ! may be used instead of AND, OR, and NOT notation. The "+" or required operator stipulates that the term after the "+" symbol must match the document. To search for documents that must contain "Zend" and may contain "Framework" use the query: The "-" or prohibit operator excludes documents that match the term after the "-" symbol. To search for documents that contain "PHP framework" but not "Zend Framework" use the query: If no operator is used, then the search behavior is defined by the "default boolean operator". This is set to OR by default. That implies each term is optional by default. It may or may not be present within document, but documents with this term will receive a higher score. To search for documents that requires "PHP framework" and may contain "Zend Framework" use the query: The default boolean operator may be set or retrieved with the Zend_Search_Lucene_Search_QueryParser::setDefaultOperator($operator) and Zend_Search_Lucene_Search_QueryParser::getDefaultOperator() methods, respectively. These methods operate with the Zend_Search_Lucene_Search_QueryParser::B_AND and Zend_Search_Lucene_Search_QueryParser::B_OR constants. Java Lucene and Zend_Search_Lucene support using parentheses to group clauses to form sub queries. This can be useful if you want to control the precedence of boolean logic operators for a query or mix different boolean query styles: Zend_Search_Lucene supports subqueries nested to any level. Lucene also supports using parentheses to group multiple clauses to a single field. To search for a title that contains both the word "return" and the phrase "pink panther" use the query: Lucene supports escaping special characters that are used in query syntax. The current list of special characters is: + - && || ! ( ) { } [ ] ^ " ~ * ? : \ + and - inside single terms are automatically treated as common characters. For other instances of these characters use the \ before each special character you'd like to escape. For example to search for (1+1):2 use the query: