@@ -39,17 +39,17 @@ public interface EndpointSynonym {
3939 *
4040 * Create or update multiple [Synonym].
4141 * This method enables you to create or update one or more [Synonym] in a single call.
42- * You can also recreate your entire set of [Synonym] by using the [replaceExistingSynonyms ] parameter.
42+ * You can also recreate your entire set of [Synonym] by using the [clearExistingSynonyms ] parameter.
4343 * Note that each [Synonym] object counts as a single indexing operation.
4444
4545 * @param synonyms List of [Synonym] to save.
4646 * @param forwardToReplicas By default, this method applies only to the specified index. By making this true,
4747 * the method will also send the synonym to all replicas. Thus, if you want to forward your synonyms to replicas
4848 * you will need to specify that.
49- * @param replaceExistingSynonyms Forces the engine to replace all synonyms, using an atomic save.
49+ * @param clearExistingSynonyms Forces the engine to replace all synonyms, using an atomic save.
5050 * Normally, to replace all synonyms on an index, you would first clear the synonyms, using clearAllSynonyms,
5151 * and then create a new list. However, between the clear and the add, your index will have no synonyms.
52- * This is where replaceExistingSynonyms comes into play.
52+ * This is where clearExistingSynonyms comes into play.
5353 * By adding this parameter, you do not need to use [clearSynonyms], it’s done for you.
5454 * This parameter tells the engine to delete all existing synonyms before recreating a new list from the synonyms
5555 * listed in the current call. This is the only way to avoid having no synonyms, ensuring that your index will
@@ -59,7 +59,7 @@ public interface EndpointSynonym {
5959 suspend fun saveSynonyms (
6060 synonyms : List <Synonym >,
6161 forwardToReplicas : Boolean? = null,
62- replaceExistingSynonyms : Boolean? = null,
62+ clearExistingSynonyms : Boolean? = null,
6363 requestOptions : RequestOptions ? = null
6464 ): RevisionIndex
6565
0 commit comments