You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if you transport the database from an environment with correctly configured schemas to an environment without indexes setup, it doesn't check that the schema in the database matches the schema in elasticsearch.
This task is to enhance the startup routine with a check to see if the schema of the active version doesn't exist:
curl -X GET "localhost:9200/users-4/_mapping/_doc"
{"error":{"root_cause":[{"type":"type_missing_exception","reason":"type[[_doc]] missing","index_uuid":"_na_","index":"_all"}],"type":"type_missing_exception","reason":"type[[_doc]] missing","index_uuid":"_na_","index":"_all"},"status":404}
Then, if it doesn't exist, it PUTs the schema/mapping from the database into elasticsearch.
The text was updated successfully, but these errors were encountered:
Currently, if you transport the database from an environment with correctly configured schemas to an environment without indexes setup, it doesn't check that the schema in the database matches the schema in elasticsearch.
This task is to enhance the startup routine with a check to see if the schema of the active version doesn't exist:
Then, if it doesn't exist, it PUTs the schema/mapping from the database into elasticsearch.
The text was updated successfully, but these errors were encountered: