OCT-169: fix migration of ES index #18374
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
The migration is executed asynchronously.
Before the doctrine migration was executed, the webhook consumer started indexing new documents in the index
akeneo_connectivity_connection_events_api_debug
, with a new propertyid
.Because you can index documents without configuring a mapping beforehand, the new property has been automatically created by ES with the type
text
instead ofkeyword
.In ES, you cannot directly change the type of a property. (see https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-mapping.html#updating-field-mappings)
The migration is failing for customers having sent webhooks between the deployment and the doctrine migration execution.
The dirty solution
Since we cannot rename a property, cannot change the type of a property, cannot remove a property of an existing index without re-indexing everything, and we cannot re-index this particular index.
Here what's happening in the new migration:
id
property already existssource
+dest
)Definition Of Done (for Core Developer only)