-
Type:
Story
-
Status: Backlog
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Search Infrastructure > Framework
-
Labels:None
-
Epic/Theme:
-
Story Points:4
-
Epic Link:
-
Sprint:Search | S02 Sprint 2, Search | S02 Sprint 3, Search | S02 Sprint 4, Search | S02 Sprint 5, Search | S02 Sprint 6, Search | S02 Sprint 7, Search | S02 Sprint 8, Search | S02 Sprint 9, Search | S02 Sprint 10, Search | S02 Sprint 11
-
Git Pull Request:
Sort infrastructure currently requires not only the field name, but also often a `_sortable` suffix. This is asymmetrical and counter-intuitive: a developer will index content into a `foo` field, then find out the actual field name to sort on is a variation like `foo_sortable` or `foo_Number_sortable`.
This Story intends to improve Sort infrastructure to make field name usage consistent and intuitive. It will also improve performance by avoiding duplicate fields wherever possible, and sorting directly on the original field if its type permits.
- depends on
-
LPS-91243 New Sort subsystem
-
- Closed
-
-
LPS-84968 As a developer, I want to define Search fields with types, to optimize behavior
-
- Backlog
-
-
LPS-85176 DocumentTest: convert integration test to unit tests
-
- Closed
-
-
LPS-91263 Sort subsystem: separate interfaces from implementation
-
- Closed
-
- is a dependency of
-
LPS-83586 Solr fails DocumentTest sorting integration tests
- Closed
-
LPS-67362 Move field mapping definitions to Field Registry, away from search engine specific files
-
- Open
-
-
LPS-52460 As a search developer, I would like to ensure date fields can be sorted properly in elastic and solr
-
- Closed
-
- is related to
-
LPS-118240 Not possible to set a "_score" sort in asc
- Closed