Search results in the web application and API returns different results #4506
Unanswered
shusterboris
asked this question in
Q&A
Replies: 2 comments 2 replies
-
Has anyone encountered such a problem? |
Beta Was this translation helpful? Give feedback.
2 replies
-
Hi, Vladimir. Thank you for response.
Unfortunately, not. I checked it.
Respectfully, Boris
вт, 19 дек. 2023 г., 12:29 Vladimir Kotal ***@***.***>:
… Does this also happen right after the webapp is redeployed/appserver
restarted ? I am asking to see if this could be caused by stale
IndexSearcher object perhaps.
—
Reply to this email directly, view it on GitHub
<#4506 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGDXRGJFRVZERVTVNHV7D2LYKFT77AVCNFSM6AAAAABAI6ZEW6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TQOJVHA3TG>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear friends!

I faced the problem that I meant in the subject.
The problem is that the search returns a different number of results depending on the source of the request: UI or API. For example
UI query is..
/search?project=q11_integ&full=odui&defs=&refs=&path=&type=&xrd=&nn=1&searchall=true
result is...
API request (using curl):
curl -k -o res.txt -v "http://localhost:8080/api/v1/search?projects=q11_integ&full=odui&maxresults=200000"
Result is:
I don't know if this matters, I observe this effect for large samples
Beta Was this translation helpful? Give feedback.
All reactions