Content refresh scheduler — scheduled incremental re-crawl#20
Merged
Conversation
- ContentRefreshScheduler (@component, gated on meilisearch.enabled): @scheduled(cron ${open-elements.content.refresh-cron:0 0 * * * *}) reruns ContentIndexer.indexSource over enabled sources. Guards: skip when globally disabled, skip while SearchReadinessState.isBootstrapping(), non-overlap via AtomicBoolean. Per-source try/catch isolates failures. - ContentRefreshSchedulerTest (real ContentIndexer + stub strategy + in-memory store + real SearchReadinessState): per-source/disabled/guards/non-overlap (re-entrancy, no threads)/fault isolation/cron externalization/new+deleted propagation. 103 tests green. - steps.md; refresh CLAUDE.md. Refs #19
…urce CI (Linux) failed with 'Schema "OE_SPRING_SERVICES" not found': Hibernate ddl-auto=update issued CREATE TABLE in the library's schema without creating the schema first (passed locally by luck of the shared in-memory DB / order). Fix deterministically: - hibernate.hbm2ddl.create_namespaces=true so Hibernate creates entity schemas - H2 INIT=CREATE SCHEMA IF NOT EXISTS OE_SPRING_SERVICES as a hard guarantee Refs #19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ContentRefreshSchedulerperiodically re-runs incremental ingestion over all enabled sources viaContentIndexer.indexSource, on the configurablerefresh-cron(default hourly, using@EnableSchedulingfrom spec 001). It skips while the pipeline is disabled or Meilisearch is bootstrapping, never overlaps runs, and isolates per-source failures. Relies on the indexer'slastmod/304 diff, so a no-change refresh is cheap.Spec
docs/specs/010-content-refresh-scheduler/{design,behaviors,steps}.mdTest coverage
ContentIndexer+ stub strategy + in-memory store (no mocks). 103 tests total; spec-review and quality-review clean.Closes #19
🤖 Generated with Claude Code