oracle/opengrok

provide a way to archive project/repository

Open

#1865 opened on Nov 6, 2017

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Java (4,060 stars) (747 forks)batch import
UIenhancementhelp wanted

Description

In our internal deployment there are some projects which are basically historical however still need to be present to perform searches. For these, it does not make any sense to index them since they no longer receive any changes. The indexing only incurs unnecessary I/O and CPU load. Thus, having a "archived" flag that would avoid indexing for these projects/repositories. Something similar to what is being proposed for history in #1728.

Contributor guide

Tech stack
java
Domain
backendsearch
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaOpenGrok indexing logic
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the existing indexing pipeline in OpenGrok, located in the Indexer class and related configuration files. The issue references #1728 for history, which may provide a pattern for implementing an 'archived' flag. Start by examining the project's configuration handling to add a boolean field, then modify the indexing loop to skip repositories with that flag set. Check the IndexDatabase and Repository classes for relevant code.