feat: add support for qlever full text search#389
Draft
recalcitrantsupplant wants to merge 1 commit intomainfrom
Draft
feat: add support for qlever full text search#389recalcitrantsupplant wants to merge 1 commit intomainfrom
recalcitrantsupplant wants to merge 1 commit intomainfrom
Conversation
recalcitrantsupplant
force-pushed
the
david/support-qlever-fts
branch
from
07ec7ff to
bcd4a6f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Search string is split into short (<=3) and long (>3) words. The short words each produce a FILTER(CONTAINS expression which does not contribute to search result weighting. The long words produce the SERVICE clause pattern qlever uses.
Draft pending further testing.
Long word filtering appears to miss some terms - requires further investigationThis was a UI issue, data was being returned correctly