I was just curious if anyone here is actually using Nextcloud’s Elasticsearch as FulltextSearch?
I have used it before - and it IS flakey…
Worked for half a year, then stopped working and I can’t get it to work… It will start, but sometime in the middle of a index run will quit with a load of errors in PHP…
Components have all being updated, like the tesserect component, but still will not work. And I did try different things on different servers…
A search in NC will only find something if eg a filename contains that string, but NOTHING from inside a file is shown, not even a simple textfile is indexed…
My 2 cents
my 50 cts:
Nextcloud: ElasticSearch: Memory usage and ParamsModel::Incomplete line
Otherwise I have the same symptoms as you do. Additionally the mysterious file locks:
I think that an integrated full text search is essential for such a system and I am surprised that the NC guys pay so little attention to it.
As said, the File Locks are probably files in the process of OCR with Tesserect OCR - and “scanning” a 20 page PDF can take a while longer than a reading a textfile…
However, not even a textfile is correctly indexed…
I quite agree that a working search is essential for such a system. Using local search is NOT an alternative, as a lot of users only have the web obtion on the road…
I’ve found something at the nextcloud forum.
Hello all, since the update to Nextcloud 20 my Elasticsearch instance is not working properly. I have updated the three plugins needed by Nextcloud in order to make Elasticsearch work. I have already tried to purge elasticsearch installation and...
Reading time: 6 mins 🕑
Likes: 2 ❤
Also have a look here:
05:27PM - 07 Jan 21 UTC
03:52PM - 05 May 21 UTC
Steps to reproduce
Create a new file via webinterface (e.g. readmx.docx)
Delete or rename the file
Operating system: # CentOS7
uname -a: Linux...