After you add a data source, add or modify an index table, or add or update advanced configurations, you must Update Configurations and then perform reindexing to apply the changes.
On the O&M Management page, click Update Configurations and then Reindexing at the top of the page.
-
Select the index structure version to update, including the versions of the index tables in the corresponding data source. Then, select the advanced configuration version and specify whether to automatically trigger reindexing. The Update Instance Configurations page contains configuration items such as Index Structure Version (for selecting data source and index table versions), Advanced Configuration Version, and Push Configuration and Trigger Reindexing.
Note:
-
You can select only one data source for each configuration update. Within that data source, you can select multiple index tables to update.
-
If you have multiple clusters, the configuration update applies to all clusters by default.
-
If you choose to automatically trigger reindexing for a MaxCompute data source, you must select a specific partition.
In the Reindexing Data Source configuration table, click the drop-down list in the Data Partition/Timestamp column and select the required partition value, such as
pt=20211112. -
If you choose to automatically trigger reindexing and have configured an API data source, you can set the Data Source option to Empty Data or Restore Data from Index. To retain all data from the current full version, select Restore Data from Index and then choose a data recovery version.
In the Reindexing Data Source configuration for an API data source, the Data Source option can be set to Empty Data or Restore Data from Index. If you select Restore Data from Index, you must select the full version to restore from the Data Recovery Version drop-down list.
Important-
The timestamp cannot be later than when data was last pushed to the API data source.
-
-
-
-
After pushing the configuration, navigate to O&M Center > Change History to view the update's progress.
The Change History page displays pipeline execution records. A Manual Full Rebuild record includes five stages: init, trigger, scan, build, and switch. Each stage shows a status of Completed, In Progress, or Not Started. The area below the stages displays metadata such as the data center, data source, trigger method, and generation. A Push Configuration record includes three stages: init and check, update worker info, and trigger build. A Details link is available under each stage. The area below the stages displays metadata such as the configuration type, data center, and version.
Pushed configurations become available in production only after the full build completes.