Page MenuHomeSoftware Heritage

Redesign origin search using a dedicated component (swh-search)
Closed, ResolvedPublic

Description

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.

Related Objects

StatusAssignedTask
OpenNone
Work in Progressvlorentz
Openvlorentz
Resolvedvlorentz
Resolvedvlorentz
OpenNone
Resolvedvlorentz
Resolvedvlorentz
Resolvedolasd
Resolvedvsellier
Resolvedvlorentz
Resolvedardumont
Duplicateolasd
Resolvedvlorentz
Resolvedvsellier
Resolvedvlorentz
Resolvedvlorentz
Resolvedvlorentz
Resolvedvsellier
Resolvedvsellier
Resolvedvlorentz
Resolvedvsellier
Resolvedvsellier
Resolvedvlorentz
Resolvedvsellier
Resolvedardumont
Resolvedardumont
Resolvedvsellier
Resolvedvsellier
Resolvedvsellier
Resolvedvsellier
Resolvedvsellier
Resolvedvsellier
Resolvedanlambert
Resolvedvlorentz
Resolvedvsellier
Resolvedvsellier
Resolvedvsellier

Event Timeline

vlorentz triaged this task as Normal priority.Jul 10 2019, 4:56 PM
vlorentz created this task.
vlorentz changed the task status from Open to Work in Progress.Dec 20 2019, 3:26 PM
ardumont renamed this task from Redesign origin search using a dedicated component to Redesign origin search using a dedicated component (swh-search).Jan 24 2020, 9:28 AM
ardumont changed the status of subtask T2167: Deploy swh-search from Open to Work in Progress.Jan 24 2020, 9:38 AM