nextcloud / nextcloud/fulltextsearch

occ config:app:set fulltextsearch search_platform value changed :-(

Open
#600 7 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
234
Forks
64
Avg merge
6h 18m
Merged PRs (30d)
10

Description

To whom it may concern:

I just had to learn that the value of the occ config:app:set fulltextsearch search_platform command changed from FullTextSearch_ElasticSearch to FullTextSearch_Elasticsearch (It's the "s" in search.)

For people using the web gui to setup nextcloud that might not be a big thing.

For automation you want to avoid such "typos" or " typo corrections". Because it breaks your scripts/playbooks.

https://github.com/ReinerNippes/nextcloud/commit/37a40e64b4d3bf80c6edfe91429412cb673c1611#diff-4ce6d64954ed973ef2ff29ad3971eeaab810b931d0377b596114b8d0e0a7307a

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the occ config:app:set fulltextsearch search_platform entry point and review the referenced commit. Trace how the old and new search_platform spellings are handled, then identify the expected behavior for automation and cover it with an appropriate test.

Written by the indexing model from the issue text.

Assessment

Tech stack
elasticsearch, php
Domain
backend, search
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.