-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Inconsistent Search Results Behaviour #15934
Comments
cc: @phlax |
@zachmandeville thanks for reporting ive noticed that the search is not very good on a number of occasions - tbh ive never been that impressed with sphinx's search there are a few search settings set in the i think there is also a search adapter that you can add to further customize, which may be useful in resolving specific issues - https://www.sphinx-doc.org/en/master/usage/advanced/websupport/searchadapters.html if you were to experiment with these and PR any improvements i would be very up for reviewing - otherwise i will take a look at this as i have time |
Thank you for these resources! I'll do some experimenting as time permits. |
Upstream fix as sphinx-doc/sphinx#8070 |
@daixiang0 it would be good to know whether this bug is now fixed by upgrade to sphinx 4 |
I update the pr and I test in latest doc website with "ip tag", it works. |
great, thanks @daixiang0 |
Title:
On the envoy docs, search results are inconsistent across similar search terms.
Description:
I noticed when searching for ip tagging, that I could only find the page when i matched text in the qualified names referenced on the page. Other pages I could find by matching any text on the page.
Repro steps:
.
I reproduced the below behaviour on firefox, chrome, and safari. I did not test on all versions, but reproduced using latest, 1.17.1, 1.16.1, and 1.13.1
The first set of terms will not bring up the ip tagging page. "iptag" will return the page by matching on the qualified names in the page. Any of the last terms will bring up the correct kafka broker page among its results.
Admin and Stats Output:
n/a
Config:
n/a
Logs:
n/a
Call Stack:
n/a
The text was updated successfully, but these errors were encountered: