-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
When booting Optimize, the OpenSearch schema is able to check and update existing indexes, write/update the metadata by using the metadata service and is able to write/read the Optimize License
Testing Notes
- Run
docker-compose -f docker-compose.yml --profile opensearch up -d
- Start Optimize with
SPRING_PROFILES_ACTIVE=opensearch
- The startup will fail and that's ok, BUT...
- Check that all indexes were created in opensearch
- For that check first the log messages during startup and see if there are logs of indexes being created and ultimately "Opensearch schema initialized successfully"
- Check the Opensearch database with your favorite browser extension in localhost:9205 and see if the indexes are indeed there
- Take some samples and check if mappings and aliases are created properly, e.g.
GET http://localhost:9205/INDEX_ALIAS_OR_NAME_HERE/_mappings
GET http://localhost:9205/INDEX_ALIAS_OR_NAME_HERE/_alias
- Shutdown optimize
- Restart optimize
- Watch that no new errors show up in the logs
- Do the same verifications as described in step 2 and make sure that everything is working the same
This is the controller panel for Smart Panels app
- depends on
-
OPT-7348 Create abstraction layer for ElasticSearch Schema
- Done
-
OPT-7349 OpenSearch Schema gets created when first booting Optimize
- Done
- is depended on by
-
OPT-7352 Clean up OpenSearch Client infra-structure after implementing OpenSearch Schema
- Backlog
- is related to
-
OPT-7348 Create abstraction layer for ElasticSearch Schema
- Done
-
OPT-7349 OpenSearch Schema gets created when first booting Optimize
- Done
- links to