An encryptionKey section contains a user-defined keyVaultKeyName (required), a system-generated keyVaultKeyVersion (required), and a keyVaultUri providing the key (required, also referred to as DNS name). Available for billable search services created on or after. Used to encrypt a synonym map, with your own keys, managed in your Azure Key Vault. Synonym rules separated by the new line ('\n') character. Only Apache Solr format ( solr) is currently supported. A synonym map name must only contain lowercase letters, digits or dashes, cannot start or end with dashes and is limited to 128 characters. Request contains the following properties: Property The following JSON is a high-level representation of the main parts of the definition. The body of the request contains a synonym map definition, which includes the format of the synonym map and the list of rules in the specified format. You can find the API key in your search service dashboard in the Azure portal. Create requests must include an api-key header set to your admin key (as opposed to a query key). It is a string value, unique to your service. The api-key is used to authenticate the request to your Search service.
The following table describes the required and optional request headers. The current stable version is api-version=. After starting the name with a letter or number, the rest of the name can include any letter, number and dashes, as long as the dashes are not consecutive. The name must be lower case, start with a letter or number, have no slashes or dots, and be less than 128 characters.
Set this to the unique, user-defined name of your search service. For more information, see Service limits. The maximum number of synonym maps that you can create varies by pricing tier.
0 kommentar(er)
