| Summary: | Layer index: allow searching the metadata | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Layer Index | Reporter: | Paul Eggleton <bluelightning> |
| Component: | Layer Index | Assignee: | Unassigned <unassigned> |
| Status: | NEW --- | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | Low | CC: | akuster, brian.avery, jose.perez.carranza, mingli.yu, randy.macleod, tim.orling, william.lyu |
| Version: | 6.99 | ||
| Target Milestone: | Future | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Paul Eggleton
2015-11-11 15:58:10 UTC
Not sure if this works or if we want to implement this. This has not yet been implemented. I think it would still be useful though. Low/Future correctly reflects the priority. Our current search is based entirely on what is available in the admin interface and the default REST API coming from Django rest framework https://www.django-rest-framework.org/ Some more capable searches could be done with https://django-filter.readthedocs.io/en/stable/ but that does not come for free. Some additional code would need to be written and would likely be brittle? There is also some support that would need to be integrated and assumes a Postgres backend, which is not what we are running in production: https://docs.djangoproject.com/en/5.0/ref/contrib/postgres/search/ Actual full text search would probably need something more like ElasticSearch https://django-elasticsearch-dsl.readthedocs.io/en/latest/ which would add additional infrastructure needs (adding an actual Elastic Search or Elastic Stack server/service). Still valid. Moving to 6.99. |