-
Notifications
You must be signed in to change notification settings - Fork 59
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
0 hits in search results #488
Comments
I confirm this issue too. large collections break the code. |
If it does this, you can 'cut' your search from the search field and let it reset to show everything, then paste in your search again and it should work. It is somewhat intermittent on when it decides to do that. |
@rg-software @kouroshshafi do you see any error messages in the browser console? For the 800k collection, were you still using SQLite? |
Well, it's been a while... Sorry for the unrelated report, but I tried to change the backend to Elastic Search, and now I do not have the "zero hits" issue. |
I installed the Linux Docker image of SIST2, made it running (shows v3.4.2-SQLite).
Tried to index a couple of small collections in SQLite mode, works fine.
Next, indexed a larger collection (around 800,000 files), and now whatever I type in the search box, the system produces zero hits.
When the search box is empty, I see the files, so the collection seems to be indexed fine.
"Filter path" button also shows all the paths correctly. Even if I uncheck the large collection and leave only the small collection, no search results pop up.
Is there anything I can do to diagnose the issue? I don't see anything relevant in frontent-default.log, for example.
The text was updated successfully, but these errors were encountered: