Skip to content
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

Open
rg-software opened this issue Jul 13, 2024 · 4 comments
Open

0 hits in search results #488

rg-software opened this issue Jul 13, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@rg-software
Copy link

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.

@rg-software rg-software added the bug Something isn't working label Jul 13, 2024
@kouroshshafi
Copy link

I confirm this issue too. large collections break the code.

@dpieski
Copy link
Contributor

dpieski commented Dec 26, 2024

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.
~5mil docs here.

@simon987
Copy link
Collaborator

@rg-software @kouroshshafi do you see any error messages in the browser console?

For the 800k collection, were you still using SQLite?

@rg-software
Copy link
Author

rg-software commented Jan 11, 2025

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 have another trouble instead. If I move a file from FolderA to FolderB, after reindexing the system finds BOTH entries (with the first link naturally broken). The only way to get rid of a broken link is to do full reindexing, which takes 2 days in my case. (moved to #506)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants