Origin search is currently written as a substring/regexp search in postgresql. This is not optimal, and won't work with alternative storage backends (eg. Cassandra)
We should use a component dedicated to text search, eg. ElasticSearch.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | vlorentz | T1892 Cassandra as a storage backend | ||
| Resolved | vlorentz | T2185 Make webapp0 use Cassandra as storage backend. | ||
| Resolved | vlorentz | T2186 Merge swh-storage-cassandra in swh-storage master | ||
| Open | None | T1523 Search tools on metadata | ||
| Work in Progress | vlorentz | T1910 Redesign origin search using a dedicated component (swh-search) | ||
| Resolved | olasd | T2052 Publish swh-search on PyPI | ||
| Open | vlorentz | T2182 Switch production swh-web to use swh-search instead of postgresql search. | ||
| Resolved | vlorentz | T2183 Switch webapp0 to use swh-search instead of postgresql search. | ||
| Resolved | ardumont | T2167 Deploy swh-search | ||
| Duplicate | olasd | T2174 Add debian package for swh-search | ||
| Resolved | vlorentz | T2184 Replay origins to ElasticSearch's "origin" index |