Skip to content

WIP: ADR on Search Backend#727

Draft
koppor wants to merge 4 commits into
mainfrom
add-adr-on-db-backend
Draft

WIP: ADR on Search Backend#727
koppor wants to merge 4 commits into
mainfrom
add-adr-on-db-backend

Conversation

@koppor

@koppor koppor commented Jun 19, 2026

Copy link
Copy Markdown
Member

Aim

Solid ADR on the backend.

Therefore

  • solid list of requirements covering our cases (regex based search, substring serach, ...)
  • running Java programs "trying out" things.

Checklist

  • I own the copyright of the code submitted and I license it under the MIT license
  • [.] If AI tools were used, I disclosed them in the "AI usage" section and reviewed, understood, and take full ownership of all AI-generated code
  • [.] I manually tested my changes in running JabRef (always required)
  • [.] I added JUnit tests for changes (if applicable)
  • [.] I added screenshots in the PR description (if change is visible to the user)
  • [.] I added a screenshot in the PR description showing a library with a single entry with me as author and as title the issue number
  • [.] I described the change in CHANGELOG.md in a way that can be understood by the average user (if change is visible to the user)
  • [.] I checked the user documentation for up to dateness and submitted a pull request to our user documentation repository

koppor and others added 4 commits June 19, 2026 05:38
State the thread's Lucene-for-search + SQLite-for-storage recommendation explicitly and justify diverging to single-technology SQLite-FTS5, including a rebuttal of the
  Zotero 'SQLite FTS bloats past ~30k items' precedent. Add an 'Also considered and rejected' table for the wider 13-technology sweep, link the recommendation comment from the
  ADR, and record Citavi/Mendeley plus the Zotero-scaling clarification in the SQLite evaluation.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
tests-manual/search-backend-mwe: a jbang suite to close ADR 0064's measurement gates. First candidate is the SQLite regex gate (naive REGEXP UDF scan vs
  literal-extraction trigram pre-filter, across a selectivity-spanning query set), on a shared deterministic data generator and a common timing/CSV harness, with a pinned Docker
  runner for resource-capped/arm64 runs. Adds a GitHub Actions workflow triggered manually (workflow_dispatch) and on changes to the suite (push/pull_request).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant