-
Notifications
You must be signed in to change notification settings - Fork 18
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
Revisit unfielded query mapping to author search #174
Comments
Do we want strings in quotes to not be expanded at all? That is, we'd broadcast them as-given across all fields that an unfielded search would match. Even then I think the author name tokenizer would likely cause the same issue? |
I'm not sure I understand the question, so let me restate it as such and see if we agree. An quoted unfielded search ( The problem of this query really lies in the fact that the above query generates, among others, a search for |
Note: the solution to this may simply be a fix to the author parsing strategy (see #194), so we should work on that first |
The working solution for #194 is to ensure that the resulting query doesn't contain fewer than the number of terms it began with: "Anna Kelbert" contains 2 terms and should never map to "Kelbert, *" which only contains 1, but it could map to both "Kelbert, Anna" and "Anna Kelbert, *". For your example "Kepler 1362 b" would contain 3 terms and could not be expanded to include a 1 term wildcard query like "b, *". |
Currently a query of
"Kepler 1362 b"
gets rewritten by our modified edismax into something that includesauthor:b, *
. This is clearly undesirable, so we should reconsider the rewriting rules to avoid this chain of eventsThe text was updated successfully, but these errors were encountered: