diff --git a/docs/tutorial/IndexAugmenter.md b/docs/tutorial/IndexAugmenter.md index 23ad719af3f1471c9634226921107baad72e91a1..f12a827603460c609f7377f55f3ebd8850a9124d 100644 --- a/docs/tutorial/IndexAugmenter.md +++ b/docs/tutorial/IndexAugmenter.md @@ -325,9 +325,6 @@ the records from the `OSDU search` results, any one of the following mistakes ca * The feature flag `index-augmenter-enabled` for `Index Augmenter` is not enabled in the given data partition. Please check with the service provider. -* If the extended properties are created in the data records but those extended properties are not searchable, the option `force_clean` for re-index - is not set to `True`. - * Any one of the mandatory properties is missing, such as `data.Code`, `data.Configurations[].Name`, `data.Configurations[].Policy` or `data.Configurations[].Paths[].ValueExtraction.ValuePath` and etc. diff --git a/docs/tutorial/IndexerService.md b/docs/tutorial/IndexerService.md index f63d8c72510c6103c97c53bc93566d19030b5449..6ab6651d222496d7aab9594358d9a95245883fd0 100644 --- a/docs/tutorial/IndexerService.md +++ b/docs/tutorial/IndexerService.md @@ -153,8 +153,7 @@ Users must be a member of `users.datalake.admins` or `users.datalake.ops` group. #### Query parameters `force_clean` <br /> -  (optional, Boolean) If a kind has been previously indexed with a schema and if you wish to apply latest schema changes before re-indexing, than use this query parameter. It will drop the current Index schema, apply latest schema changes & re-index records. If `false`, reindex API -will use the same schema and overwrite records with the same ids. Default value is `false`. +  (optional, Boolean) If there is any inconsistency between the storage records and the index records, you can use this query parameter to synchronize them. If `true`, it will drop the current index data, apply latest schema changes & re-index records. If `false`, reindex API will apply the latest schema and overwrite records with the same ids. Default value is `false`. #### Request body