Problem statement

1. Solr is not the solution that fits perfectly every-time. U.S. team didn't have Solr in their new infrastructure setup, Alexey from LD told that customizing Solr to client requirements could be hard.
2. Installing and setting up Solr could be a friction point during the installation process.

Hypothesis

1. It's possible for CKAN to work with top-3 most popular search engines now and integrate other less-known search solutions (Providing the ability of using any other search engine will make work of integrators and developers easier and will enable new use cases for CKAN).
2. It's possible to implement default lightweight search solution that requires no or minimal setup effort from the user (By having a lightweight default solution we cover up simplification in the installation process so that anyone has a basic solution right away).

Discovery work
Log here everything you've found during the discovery

Validation
Why the solution is trustworthy? What makes it strong?

Questions to consider:

• Is this change going to break current installations?

• Can we provide a backwards compatibility?

• How easy is gonna be for current implementations to migrate to this new release?

• Do current versions of CKAN have the adequate resources/support to migrate to this new version?

• Are we going to change the database schema?

• Are we going to change the API?

• Are we going to deprecate Interfaces?