-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider the new JSON fields for Tantivy full-text search #336
Comments
joepio
pushed a commit
that referenced
this issue
Feb 21, 2023
joepio
pushed a commit
that referenced
this issue
Feb 21, 2023
joepio
added a commit
that referenced
this issue
Feb 21, 2023
joepio
added a commit
that referenced
this issue
Feb 21, 2023
joepio
pushed a commit
that referenced
this issue
Feb 21, 2023
joepio
pushed a commit
that referenced
this issue
Feb 21, 2023
joepio
added a commit
that referenced
this issue
Feb 21, 2023
joepio
added a commit
that referenced
this issue
Feb 21, 2023
joepio
pushed a commit
that referenced
this issue
Feb 21, 2023
joepio
pushed a commit
that referenced
this issue
Feb 21, 2023
joepio
added a commit
that referenced
this issue
Feb 21, 2023
joepio
added a commit
that referenced
this issue
Feb 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Relates to #40 #210
The new 0.17 release of the Tantivy crate features JSON support.
Current situation
Currently, we have a custom way of indexing, which uses individual triples. This has some serious downsides, such as that if a document has multiple hits in various properties (e.g. hit in Title and Desription field), we cannot combine these and increase its weight.
Opportunities:
get_resource_extended
), which includes members in collections, maybe?Implementation suggestion
server/search.rs
, change theadd_resource
. Instead of iterating over all prop_vals, just index the fullJSON-AD
.build_schema
now needs ajson
field.name
, perhaps only fuzzy that field + description in default UIThe text was updated successfully, but these errors were encountered: