nextcloud / nextcloud/fulltextsearch
fulltextsearch:search causes exception
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 234
- Forks
- 64
- Avg merge
- 6h 18m
- Merged PRs (30d)
- 10
Description
FulltextSearch doesn't search anything and causes an exception.
sudo -u apache php /var/www/html/nextcloud/occ fulltextsearch:search user test
search
In Connection.php line 632:
{"error":{"root_cause":[{"type":"x_content_parse_exception","reason":"[1:63] [bool] failed to parse field [should]"}],"type":"x_content_parse_excep
tion","reason":"[1:63] [bool] failed to parse field [must]","caused_by":{"type":"x_content_parse_exception","reason":"[1:63] [bool] failed to parse
field [should]","caused_by":{"type":"x_content_parse_exception","reason":"[1:63] [bool] failed to parse field [should]","caused_by":{"type":"illeg
al_state_exception","reason":"expected value but got [START_ARRAY]"}}}},"status":400}
Nextcloud 18.0.4
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
Reproduce the failure with sudo -u apache php /var/www/html/nextcloud/occ fulltextsearch:search user test, then inspect Connection.php around line 632 and the code building the search request. Confirm the query no longer raises the reported parse exception and that the command returns search results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- search
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100