ElasticSearch index with multiple types needed on Symfony
Budget: $30 – $250 USD
We have a project written in Symfony that also utilises technologies such as ElasticSearch and RabbitMQ. We recently updated ElasticSearch and now it only supports a single mapping type per index only.
We have a bunch of resources deals, events, workshops etc with different models
Previously in elasticsearch we had a single index with multiple types (one for each resource)
The symfony app has a search and these different types (resources) and they had different weighting but would all show up in search.
In a later release of elasticsearch (6.8 perhaps) - they got rid of type mapping https://www.elastic.co/blog/removal-of-mapping-types-elasticsearch
And the index would no longer populate!
So we are now faced with two solutions - have each resource type in it's own index and change the search to interrogate multiple indexes
Or... change to a single index that has common data and has a field to mark what resource type it is.
The second seems like more work
We are looking for guidance in this (we will want to upgrade to ES7 at some point in the near future) and will have additional work on the project for anyone that can help us resolve this first issue.
It is using the FOS Elastica bundle currently and populating from the ORM.
We have a bunch of resources deals, events, workshops etc with different models
Previously in elasticsearch we had a single index with multiple types (one for each resource)
The symfony app has a search and these different types (resources) and they had different weighting but would all show up in search.
In a later release of elasticsearch (6.8 perhaps) - they got rid of type mapping https://www.elastic.co/blog/removal-of-mapping-types-elasticsearch
And the index would no longer populate!
So we are now faced with two solutions - have each resource type in it's own index and change the search to interrogate multiple indexes
Or... change to a single index that has common data and has a field to mark what resource type it is.
The second seems like more work
We are looking for guidance in this (we will want to upgrade to ES7 at some point in the near future) and will have additional work on the project for anyone that can help us resolve this first issue.
It is using the FOS Elastica bundle currently and populating from the ORM.