nextcloud / nextcloud/server

Add setting to automatically execute add-missing-indices

Open
#46,046 1 comment 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage enhancement feature: install and update
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
Running add-missing-indices manually after upgrade on small instances isn't necessary, it could be run during the upgrade.

Describe the solution you'd like
Add an occ setting to automatically run add-missing-indices on upgrades. Many small instances would not be disrupted by running this on upgrades, so it would be useful to be configurable.

Describe alternatives you've considered
Running cronjobs, other types of scripts.

Additional context
There was some discussion of this on the forum here and many other forum threads about people being confused in how to run the command. For these kinds of users it would be maybe nice to have a setting in the UI to declare their instance as a "small" instance, to automatically configure things like this.

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 by tracing the occ db:add-missing-indices command and the upgrade flow mentioned in the issue. Review the linked forum discussion for expected behavior and configuration concerns. Done means the upgrade process can conditionally execute the command through a configurable setting without disrupting instances where it is disabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
backend, databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.