Search adaptions and corrections. (Working Search/Autocomplete) #13
No reviewers
Labels
No labels
area: app c
area: app d
area: devops
area: discovery
area: docs
area: proposal
area: X-device Sync
Chainquery
consider soon
dependencies
Epic
Fix till next release
good first issue
hacktoberfest
help wanted
icebox
Invalid
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
Parked
priority: blocker
priority: high
priority: low
priority: medium
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lighthouse.js#13
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Improvements to search relevancy and separation of search/autocomplete feature.
-- Removed
getSuggestion
-- Added
getResults
-- Added
getAutoComplete
-- Added Pagination via
size
andfrom
parameters.-- Added cleansing functionality for autocomplete as so it does not return undefined or duplicate values.
Restructured to search query to bool query that searches on a claims name, title, author and keywords in description --
it's a disaster
now shows in a search fordisaster
autocomplete also returned correctly for the same example.For clarity i think it is best to keep the API doing as it is requested (search end point returning search results not suggestions) -- suggestions should be returned separately ideally.
Great work, helping me out with elasticsearch!