Re-embed memories when embeddingModel changes vector size

未关闭
#2 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript
领域
databases, search

调研方向

Read DESIGN.md sections “Search and bootstrap” and “One vector space” to understand the stated constraints. Then locate the Memory model, embedding option reload handling, and vector index setup; the issue does not name their files or tests. Done means existing rows are re-embedded with the configured model and a dimension-changing reload is handled safely.

由索引模型根据 Issue 内容生成。

描述

Problem

embeddingModel can be changed in the plugin options, but rows already embedded by the previous model are not re-embedded. Harper's HNSW index fixes its vector size at the first vector, so a model with a different size:

  • leaves new and revised rows out of the vector index (Harper skips them with a warning);
  • makes vector queries fail, so search falls back to full-text only and logs it once per model;
  • keeps rows written under the mismatched model out of the vector lane even after the option is reverted, until each is revised.

Nothing rejects or warns about the change when the options reload. Same-size model switches are handled: the vector lane only compares rows tagged with the configured embeddingModel, and older rows stay reachable through full-text.

Proposed

A migration that re-embeds every Memory row with the configured model, rebuilding the vector index when its size changes, plus a check that refuses (or warns about) a dimension-changing reload until the migration runs.

Refs: the v0 core PR (DESIGN.md "Search and bootstrap", "One vector space").

Review-Deferral: 6ceee23de50a8167 severity=minor category=reliability

🤖 Generated by Claude Opus 5.5 (Claude Code); posted via @kriszyp.

主要语言
JavaScript
星标
0
派生
0
平均合并
20 小时 29 分钟
30 天内合并 PR
28

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

HarperFast/agent-memory 的其他 Issue

查看 HarperFast/agent-memory 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。