The command no longer times out after 10 minutes when the processing
hasn't been finished yet. Instead it shows progress and logs successful
and failed spaces. The process can also be aborted using ctrl+c.
Example output:
```
$ bin/opencloud search index --all-spaces --insecure --force-rescan
[1/602] indexed space a9033d65-6c13-4556-b923-f321ab33a9ca$eb6a8a0e-2e62-4b40-bce9-360063236676!eb6a8a0e-2e62-4b40-bce9-360063236676 in 5.501190908s
[2/602] indexed space a9033d65-6c13-4556-b923-f321ab33a9ca$34b7c565-da3b-4f53-8559-825e87db4011!34b7c565-da3b-4f53-8559-825e87db4011 in 5.935075697s
[3/602] indexed space a9033d65-6c13-4556-b923-f321ab33a9ca$e08c6026-24f6-4a9e-a805-ed335b34b8da!e08c6026-24f6-4a9e-a805-ed335b34b8da in 6.016350958s
^Caborted, indexing has been stopped
```
Fixes#2592
Address review feedback: now that the flag is read under its
registered name `force-rescan`, line the local variable up with the
operator-facing vocabulary. The proto field `ForceReindex` is left
untouched so the wire format stays the same.
The `opencloud search index` command registers the flag as
`--force-rescan` (see pflag registration below) but reads it via
`GetBool("force-reindex")`, so the value is always false — passing
`--force-rescan` had no effect and no force rescan was ever triggered.
Read the flag under its registered name.
That can be helpful when the search service configuration has changed,
e.g. by enabling TIKA. Previously files that had already been indexed
were not indexed again and thus were no part of the fulltext index.
Fixes#2285Fixes#2578
* Increase the timeout for indexing spaces
* Allow for making queries that are not constrained to a RootID
* Use nano precision for the Mtime
* Add a SpaceDebouncer
The debouncer can be used to delay operations on spaces until things
have settled down to avoid doing the same operation multiple times.
* Do not index subtrees until they have changed (i.e. the mtime differs)
* Also pass a user to the space debouncer func
* Trigger a rescan of the according space when an event is received
* Improve wording/logging
* Add changelog
* Get rid of superfluous GetUserByClaim call
* Fix tests
* Fix reindexing triggered by shares by using the event's SpaceOwner
* Bump reva to pull in the space owner events changes
* Fix changelog
* Fix linter issues
* Fall back to the executant if no owner was received from the event
* Bump reva and go-cs3apis
* Fix go.sum
* Bump core
* Adapt expected failures
* Tweak debounce settings
This avoids using a public global variable. It allows us to initialize
the default client a bit later (outside of init()). That way we can e.g.
properly initialize the in-memory registry.
André Duffeck