Search functionality

[iskitsas]

• Provide a REST API to search resources of CMS
• Integrate with frontend

[Sanskar95]

@iskitsas
Would there be only search by name or we can search by multiple attributes of a resource?

[iskitsas]

Hi @Sanskar95,

I would go with multiple attributes. Another solution would be to integrate ELK stack or SOLR, and build on top of that.

[Sanskar95]

@iskitsas
If we go with elastic search , we would need to migrate the existing data in MySQL to a elastic index right?

[iskitsas]

@Sanskar95
correct

[Sanskar95]

@iskitsas we can then get started with migration scripts first as part of this story , will create an issue for it.
One suggestion:
Should we create an endpoint for it in the cms application itself or a separate application?

[Sanskar95]

Linked to #26

[iskitsas]

Hi @Sanskar95 ,
The ELK stack should be on a different container. You should create auxiliary endpoints for triggering actions like re-indexing, update index etc (useful on operations). The backend should support integrations with the ES API, so you should also implement a client for this. This could be a general one, and be easily turned on or off (someone might do not want indexing). Take into account that you could provide an interface for this and easily someone to choose which implementation to use, eg ES vs SOLR.