Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

[Feature][Core] Backfill: when timeAfter moves earlier, collect only the missing period instead of restarting full sync

Ouverte
  • Quelque chose ne va pas ?
#9,246 0 commentaires 1 réaction 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
go
Domaine
data-engineering

Piste de recherche

Start with backend/helpers/pluginhelper/api/collector_state_manager.go and the duplicated SubtaskStateManager logic; trace how GetSince() and GetUntil() reach collectors. Then inspect api_collector.go, graphql_collector.go, and GitHub collectors, including workflow runs, to find flush behavior and range filters. Done means backfill fetches only the missing interval, preserves existing raw rows, and stores the earlier TimeAfter; collectors that cannot bound the range may retain full recollection.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Search before asking
  • I had searched in the issues and found no similar feature requests.
Use case

A project is first collected with timeAfter = T1. Later the user moves timeAfter to an earlier date T0 < T1 to get more history. Today this restarts the collection from scratch:

  • NewCollectorStateManager (backend/helpers/pluginhelper/api/collector_state_manager.go) sees syncPolicy.TimeAfter.Before(state.TimeAfter) and drops to full-sync mode: since = T0, isIncremental = false.
  • Every collector then fetches [T0, now], which includes [T1, now], the period that was already collected.
  • The REST and GraphQL collectors (api_collector.go, graphql_collector.go: "flush data if not incremental collection") delete all existing raw rows for the scope before fetching.

For large scopes the repeated fetch is the expensive part. GitHub workflow runs and jobs dominate API calls and run time, and the rate limit is shared by every pipeline using the same App or token. A full re-collection also leaves the scope with fewer rows until it finishes.

Description

Add a third collection mode, "backfill", used when the new timeAfter is earlier than the stored one:

  1. Collect only [T0, T1]: since = T0, with an upper bound until = state.TimeAfter.
  2. Do not flush the existing raw data.
  3. On success, store T0 as the new TimeAfter (the existing code already updates it for full syncs).
  4. Apply the same rule in SubtaskStateManager, which duplicates the logic.

Collectors need to honour the upper bound. Today only a few call GetUntil() (in the GitHub plugin, only the workflow runs collector); the rest use GetSince() alone. A backfill would add an until filter to each collector's request or stop condition, and fetch child records (reviews, comments, jobs) only for the newly found parents.

Collectors that cannot bound the range could keep today's behaviour (a full re-collect), so this can ship incrementally, starting with the state managers and one or two collectors.

Related issues

None found.

Are you willing to submit a PR?
  • Yes I am willing to submit a PR!
Code of Conduct
Langage dominant
Go
Étoiles
3.2k
Forks
830
Merge moyen
2 j 22 h
PR mergées (30 j)
49

Préparer son environnement

Ouvrir dans Codespaces

Lance le conteneur de développement du projet dans votre navigateur, avec votre propre compte GitHub.

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de apache/devlake

Toutes les issues de apache/devlake

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.