-
-
Notifications
You must be signed in to change notification settings - Fork 673
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
Remove tantivy schema strictness #1211
Comments
I agree with this ! |
PSeitz
added a commit
to PSeitz/tantivy
that referenced
this issue
Nov 25, 2021
PSeitz
added a commit
to PSeitz/tantivy
that referenced
this issue
Nov 25, 2021
fulmicoton
pushed a commit
that referenced
this issue
Nov 29, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently all fields in the data need to be defined in the tantivy schema, even if these fields should be ignored.
This can be an issue if you have a dataset with many fields and are interested in only few fields.
On the other side fields can be missing in the data while indexing, so there is some asymmetry.
For that I would propose to remove the strict schema default in tantivy and simply ignore fields which are not defined. It will also provide a lower entry barrier for new users (e.g. just indexing one field as a poke test).
The text was updated successfully, but these errors were encountered: