nextcloud / nextcloud/fulltextsearch
Unexpected JSON data scrolling when running first Index
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
I've just set this up, and the test procedure responds with all OK's, so I think I've got everything right.
What I am noticing is a bunch of scrolling, for what I'm assuming are documents that it cannot index based on the .ext of the files.
Is this normal? Something that could be filtered out?
Looks like .bmp, exe, dll, smb, 001, 002 extensions and more. I haven't seen any for anything I would expect fulltext to actually index.
{"reqId":"NLvNcoNvZDOz2w6NH74M","level":0,"time":"2021-07-20T17:50:55+00:00","remoteAddr":"","user":"--","app":"files_fulltextsearch","method":"","url":"--","message":"[debug] getPathFromRoot -- {\"path\":\"GRPFOLD Director\\/Sonar Archives\\/KML\\/MS1000_V0431\\/Record\\/Aug16,2010,04-48-32.smb\",\"userId\":\"admin\",\"entrySlash\":false,\"result\":\"GRPFOLD Director\\/Sonar Archives\\/KML\\/MS1000_V0431\\/Record\\/Aug16,2010,04-48-32.smb\"}","userAgent":"--","version":"21.0.3.1"}
{"reqId":"NLvNcoNvZDOz2w6NH74M","level":0,"time":"2021-07-20T17:50:55+00:00","remoteAddr":"","user":"--","app":"files_fulltextsearch","method":"","url":"--","message":"[debug] getPathFromRoot -- {\"path\":\"GRPFOLD Director\\/Sonar Archives\\/KML\\/MS1000_V0431\\/Record\\/Aug16,2010,05-01-30.001\",\"userId\":\"admin\",\"entrySlash\":false,\"result\":\"GRPFOLD Director\\/Sonar Archives\\/KML\\/MS1000_V0431\\/Record\\/Aug16,2010,05-01-30.001\"}","userAgent":"--","version":"21.0.3.1"}
{"reqId":"NLvNcoNvZDOz2w6NH74M","level":0,"time":"2021-07-20T17:50:55+00:00","remoteAddr":"","user":"--","app":"files_fulltextsearch","method":"","url":"--","message":"[debug] getPathFromRoot -- {\"path\":\"GRPFOLD Director\\/Sonar Archives\\/KML\\/MS1000_V0431\\/Record\\/Aug16,2010,05-01-30.002\",\"userId\":\"admin\",\"entrySlash\":false,\"result\":\"GRPFOLD Director\\/Sonar Archives\\/KML\\/MS1000_V0431\\/Record\\/Aug16,2010,05-01-30.002\"}","userAgent":"--","version":"21.0.3.1"}
After a bit of running that, it seems to go back to those files and then the "extra output" at the bottom turns to:
{"reqId":"NLvNcoNvZDOz2w6NH74M","level":0,"time":"2021-07-20T17:56:12+00:00","remoteAddr":"","user":"--","app":"files_fulltextsearch","method":"","url":"--","message":"[debug] fillIndexDocument request -- {\"document\":{\"id\":\"6699459\",\"providerId\":\"files\",\"access\":{\"ownerId\":\"\",\"viewerId\":\"\",\"users\":[],\"groups\":[],\"circles\":[],\"links\":[]},\"modifiedTime\":1281935414,\"title\":\"\",\"link\":\"\",\"index\":{\"ownerId\":\"\",\"providerId\":\"files\",\"source\":\"\",\"documentId\":\"6699459\",\"lastIndex\":1626803730,\"errors\":[],\"errorCount\":0,\"status\":28,\"options\":[]},\"source\":\"files_group_folders\",\"info\":[],\"hash\":\"\",\"contentSize\":0,\"tags\":[],\"metatags\":[],\"subtags\":[],\"more\":[],\"excerpts\":[],\"score\":\"\"}}","userAgent":"--","version":"21.0.3.1"}
Help is appreciated. It almost seems like there is some debug output that is turned on.
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
No source files or tests are named. Start by reproducing the first Index with the listed .bmp, .exe, .dll, .smb, .001, and .002 files, then inspect the fulltextsearch indexing logs and debug configuration. Done means determining whether this output is expected and identifying a specific change needed to suppress unsupported-file or debug messages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100