Thanks for Nextcloud, appreciate the vision and your work.
I have a question regarding fulltextsearch. I was wondering, is there a way to see if indexing is running? After installation, I ran fulltextsearch:index and after that, I ran fulltextsearch:live to keep index always running. I can see with ps auxf that, for instance, index is now active, but sometimes it is not visible there and when I try to run it via occ, nextcloud says that index is already running. So I am not really sure, how to properly track the status of indexing routine.
I don’t have any idea at all about how the full text search internals, but shouldn’t it just run the index when a file has been added/changed (by hooking into file-change listeners)? No point in running the index when everything is indexed…
Well, I run index when system is installed. After that, manual states that live indexing should be launched. But I still do not know, how to track the status.
I’m speculating (as it would make the most sense, but i havent bothered to check the source) that with live indexing activated, the fulltext:index is automatically run anytime a file is added/changed - by utilising event hooks in the nc app framework. In essence, if no process regards to fulltext:index is seen with ps, it means all files are currently indexed (so there is nothing to index, no process needed!), and since index live is active, it will start again any time a new file is added or updated.
You could test this by monitoring the ps output, wait untill you see nothing about fulltext:index, then still monitoring the ps, upload a bunch of files that can be indexed to see if it more or less instantly appears again (it might dissapear quickly though, id the index runs superfast).