Search API | On-Premise | Urbi Documentation

Updating search API services

  1. Make sure that a newer version of Search API service exists in the Docker Registry. See On-Premise releases.

  2. Update settings in the values-search.yaml configuration file, if necessary. See the example in the installation instructions.

  3. Run the command to update the service:

    helm upgrade --version=1.20.2 --atomic --values ./values-search.yaml search-api 2gis-on-premise/search-api
    
  1. Make sure that a newer version of Catalog APIs service exists in the Docker Registry. See On-Premise releases.

  2. Update settings in the values-catalog.yaml configuration file, if necessary. See the example in the installation instructions.

    Note:

    You can configure the process of importing new data for Catalog APIs. Use the importer settings group of the configuration file. If during a regular update of the Catalog APIs service you do not want to import new data, specify the manifest used for the previous import. However, if an application version is updated, using a new manifest is recommended.

  3. Run the command to update the service:

    helm upgrade --version=1.20.2 --atomic --values ./values-catalog.yaml catalog-api 2gis-on-premise/catalog-api
    

If automatic creation of new schemas while importing objects data is enabled (see importer settings of the configuration file), the previous data set is not used after switching to a new set. To save disk space, old data sets should be removed. You can do it automatically as follows:

  1. Set the importer.cleaner.enabled parameter to true.

  2. For the importer.cleaner.versionLimit parameter, specify the number of old data sets to keep. For example, 1 indicates that not more than 3 schemas (the current, the previous, and the temporary one created during the import) are saved in the base and all the older ones are removed. Note that this limit cannot be less than 1 - otherwise, it will be impossible to return to the previous version when needed.