Closed dpfaffenbauer closed 1 month ago
Thanks a lot for reporting the issue. We did not consider the issue as "Pimcore:Priority", "Pimcore:ToDo" or "Pimcore:Backlog", so we're not going to work on that anytime soon. Please create a pull request to fix the issue if this is a bug report. We'll then review it as quickly as possible. If you're interested in contributing a feature, please contact us first here before creating a pull request. We'll then decide whether we'd accept it or not. Thanks for your understanding.
I had the same problem several times. The problem there is the auto_create_index
feature of OpenSearch. When you already save elements and run the queue before the index is created (so the bin/console generic-data-index:update:index
command was executed OpenSearch will implicitly create the index with the default detected automatic mapping. The problem then is that in the case of the generic data index pimcore_asset
is an index alias and no real index, therefore the command will not recreate it.
The best way to avoid this is to disable the auto mapping feature - see: https://github.com/pimcore/demo-enterprise/blob/2024.x/docker-compose.yaml#L81
But I agree that we should somehow automatically detect this case and provide a option to delete this index automatically.
I don't have access to that docker compose file and that repo. can you paste the config for opensearch here please?
- action.auto_create_index=false
When I run
generic-data-index:update:index
I run into the following issue:When an index already exists, there should be an option to delete it or that the bundle uses that index and updates it. Or is there already and I just missed it?