nextcloud / nextcloud/fulltextsearch
Feature request: non-interactive mode - only error log
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
Hi,
the command occ fulltextsearch:index is interactive and always logs the current progress (Indexing/Results/Errors). There is the option no-readline which prevents interaction but the current progress log can only be suppressed via --quiet. In this case, even errors are not shown and afaik they are not accessible afterwards.
See nextcloud-aio #1694.
Please add a non-interactive mode or an option that only shows errors (and the corresponding files) once they occur.
Also please add a command or logfile to only show errors (after indexing) so users/admins can check after long-term indexing and report errors.
Greets, ManOki
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the occ fulltextsearch:index command and how its no-readline and --quiet options control progress and error output. Determine how errors are currently reported or retained, then define an error-only mode and a way to review errors after indexing, with tests covering interactive, quiet, and non-interactive behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- cli, search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100