Page Comparison

...

1. Backup existing data and Restoration:

   • Before proceeding with the upgrade, it's essential to back up all existing data and configurations to prevent data loss and ensure a smooth transition. There are several backup methods available, including:

     Snapshot and Restore: Utilizing

     In both local and Azure environments, we recommend utilizing Elasticsearch's snapshot and restore functionality for efficient and incremental backups.

   • File-Level Backup: Copying Elasticsearch data directory and configuration files to a separate location.

   • Database Dump: Exporting data from Elasticsearch indices for later restoration.

   • For this upgrade, we will utilize Elasticsearch's snapshot and restore functionality. This approach ensures comprehensive and efficient backups, minimizing downtime and data loss during the upgrade processAdditionally, in the Azure environment, you can use the rolling upgrade approach for seamless Elasticsearch node updates.

2. Upgrade Dependencies and Compatibility Testing:

   • This includes making changes to your project's pom.xml file, updating the Elasticsearch dependency to version 7.17.13, and ensuring compatibility with other components or libraries reliant on Elasticsearch.

   • In addition to upgrading Elasticsearch itself, it's essential to check compatibility of any other dependencies that are tied to the Elasticsearch version.

3. Adapt Code:

   • Address any code that relies on deprecated Elasticsearch APIs or data types. Find equivalent replacements in the 7.17.13.

   • Update field mapping syntax if necessary.

4. Post-Upgrade Validation :

   • Verify that all core functionalities of Sunbird Knowlg that rely on Elasticsearch, such as search queries and indexing, continue to work as expected.

...