Note: We do not recommend combining the = operator together with asterisk ( *) when you do exact matching. Returns search results where the property value is equal to the value specified in the property restriction. Text DateTime Integer Decimal Double YesNo Returns results where the value specified in the property restriction is equal to the property value that is stored in the Property Store database, or matches individual terms in the property value that is stored in the full-text index. Valid property operators for property restrictions Operator Search in SharePoint supports several property operators for property restrictions, as shown in Table 2. Property operators that are supported in property restrictions However, the managed property doesn't have to be Retrievable to carry out property searches. In addition, the managed property may be Retrievable for the managed property to be retrieved. The managed property must be Queryable so that you can search for that managed property in a document. See Managed and crawled properties in Plan the end-user search experience. To specify a property restriction for a crawled property value, you must first map the crawled property to a managed property. By default, Search in SharePoint includes several managed properties for documents. You must specify a valid managed property name for the property restriction. In other words, the previous property restrictions are equivalent to the following:Īuthor "John Smith" Specifying property names for property restrictions In the following examples, the white space causes the query to return content items containing the terms "author" and "John Smith", instead of content items authored by John Smith: The length of a property restriction is limited to 2,048 characters. The property restriction must not include white space between the property name, property operator, and the property value, or the property restriction is treated as a free-text query. Returns content items with the file name budget.xlsx.
Returns content items authored by John Smith. Table 1 lists some examples of valid property restrictions syntax in KQL queries. Specifying property restrictionsĪ basic property restriction consists of the following:
Using KQL, you can construct queries that use property restrictions to narrow the focus of the query to match only results based on a specified condition. However, you can use the wildcard operator after a phrase. KQL queries don't support prefix matching with the wildcard * as prefix, so you can't use the wildcard operator before a phrase in free-text queries. To specify a phrase in a KQL query, you must use double quotation marks. When you use phrases in a free-text KQL query, Search in SharePoint returns only the items in which the words in your phrase are located next to each other. KQL queries don't support prefix matching with the wildcard * as prefix. In prefix matching, Search in SharePoint matches results with terms that contain the word followed by zero or more characters.įor example, the following KQL queries return content items that contain the terms "federated" and "search": You can use just a part of a word, from the beginning of the word, by using the wildcard operator (*) to enable prefix matching. When you use words in a free-text KQL query, Search in SharePoint returns results based on exact matches of your words with the terms stored in the full-text index. If there are multiple free-text expressions without any operators in between them, the query behavior is the same as using the AND operator. To construct complex queries, you can combine multiple free-text expressions with KQL query operators.
You can construct KQL queries by using one or more of the following as free-text expressions:Ī word (includes one or more characters without spaces or punctuation)Ī phrase (includes two or more words together, separated by spaces however, the words must be enclosed in double quotation marks) This includes managed property values where FullTextQueriable is set to true.įree text KQL queries are case-insensitive but the operators must be in uppercase. When you construct your KQL query by using free-text expressions, Search in SharePoint matches results for the terms you chose for the query based on terms stored in the full-text index. You can increase this limit up to 20,480 characters by using the MaxKeywordQueryTextLength property or the DiscoveryMaxKeywordQueryTextLength property (for eDiscovery). However, KQL queries you create programmatically by using the Query object model have a default length limit of 4,096 characters. If you create the KQL query by using the default SharePoint search front end, the length limit is 2,048 characters. The length limit of a KQL query varies depending on how you create it.
0 kommentar(er)
