# Pitfall Log / 踩坑日志

项目：orneryd/NornicDB

摘要：发现 37 个潜在踩坑项，其中 4 个为 high/blocking；最高优先级：安装坑 - 来源证据：Datetime nested in a list/map parameter (UNWIND $rows … row.created_at) stored as Go-format string, not a temporal。

## 1. 安装坑 · 来源证据：Datetime nested in a list/map parameter (UNWIND $rows … row.created_at) stored as Go-format string, not a temporal

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Datetime nested in a list/map parameter (UNWIND $rows … row.created_at) stored as Go-format string, not a temporal
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/221 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 2. 安装坑 · 来源证据：Regression in 0593642: bulk Graphiti extraction triggers BuildIndexes/k-means warmup storm → CPU-bound hang (entity-res…

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Regression in 0593642: bulk Graphiti extraction triggers BuildIndexes/k-means warmup storm → CPU-bound hang (entity-resolution cosine search path)
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/222 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 3. 安全/权限坑 · 来源证据：Vector search substrate not updated on runtime writes (external vectors, EMBEDDING_ENABLED=false) — stale until restart…

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Vector search substrate not updated on runtime writes (external vectors, EMBEDDING_ENABLED=false) — stale until restart; degrades resolution during ingest
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/220 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 4. 安全/权限坑 · 来源证据：[BUG] db.index.vector.queryRelationships returns 0 rows on v1.1.7 (node path works)

- 严重度：high
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：[BUG] db.index.vector.queryRelationships returns 0 rows on v1.1.7 (node path works)
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/219 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 5. 安装坑 · 依赖 Docker 环境

- 严重度：medium
- 证据强度：runtime_trace
- 发现：安装/运行入口包含 Docker 命令：docker run -d --name nornicdb -p 7474:7474 -p 7687:7687 -v nornicdb-data:/data timothyswt/nornicdb-arm64-metal-bge:latest # amd64 / CPU only docker run
- 对用户的影响：非工程用户可能没有 Docker，启动成本明显增加。
- 复现命令：`docker run -d --name nornicdb -p 7474:7474 -p 7687:7687 -v nornicdb-data:/data timothyswt/nornicdb-arm64-metal-bge:latest # amd64 / CPU only docker run`
- 证据：identity.distribution | https://github.com/orneryd/NornicDB | docker run -d --name nornicdb -p 7474:7474 -p 7687:7687 -v nornicdb-data:/data timothyswt/nornicdb-arm64-metal-bge:latest # amd64 / CPU only docker run

## 6. 安装坑 · 失败模式：installation: [FEATURE] - Bulk Import API

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: [FEATURE] - Bulk Import API
- 对用户的影响：Developers may fail before the first successful local run: [FEATURE] - Bulk Import API
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/171 | [FEATURE] - Bulk Import API

## 7. 安装坑 · 失败模式：installation: [PROPOSAL] OKF Format import/export - RFC

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: [PROPOSAL] OKF Format import/export - RFC
- 对用户的影响：Developers may fail before the first successful local run: [PROPOSAL] OKF Format import/export - RFC
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/217 | [PROPOSAL] OKF Format import/export - RFC

## 8. 安装坑 · 失败模式：installation: v1.1.7 - Black Math

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this installation risk before relying on the project: v1.1.7 - Black Math
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.7 - Black Math
- 证据：failure_mode_cluster:github_release | https://github.com/orneryd/NornicDB/releases/tag/v1.1.7 | v1.1.7 - Black Math

## 9. 安装坑 · 来源证据：Docs: async_writes yaml examples in README + configuration.md don't match config.go (env-only)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：Docs: async_writes yaml examples in README + configuration.md don't match config.go (env-only)
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/215 | 来源类型 github_issue 暴露的待验证使用条件。

## 10. 安装坑 · 来源证据：SET silently fails on nodes that existed before v0→v2 storage migration

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：SET silently fails on nodes that existed before v0→v2 storage migration
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/190 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 11. 安装坑 · 来源证据：[FEATURE] - Bulk Import API

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：[FEATURE] - Bulk Import API
- 对用户的影响：可能阻塞安装或首次运行。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/171 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 12. 安装坑 · 来源证据：[Feature] Neo4j drop-in compatibility: accept the default "neo4j" database name and the 3-arg fulltext procedure form

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：[Feature] Neo4j drop-in compatibility: accept the default "neo4j" database name and the 3-arg fulltext procedure form
- 对用户的影响：可能增加新用户试用和生产接入成本。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/214 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 13. 安装坑 · 来源证据：[PROPOSAL] OKF Format import/export - RFC

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安装相关的待验证问题：[PROPOSAL] OKF Format import/export - RFC
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/217 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 14. 配置坑 · 可能修改宿主 AI 配置

- 严重度：medium
- 证据强度：source_linked
- 发现：项目面向 Claude/Cursor/Codex/Gemini/OpenCode 等宿主，或安装命令涉及用户配置目录。
- 对用户的影响：安装可能改变本机 AI 工具行为，用户需要知道写入位置和回滚方法。
- 证据：capability.host_targets | https://github.com/orneryd/NornicDB | host_targets=claude

## 15. 配置坑 · 失败模式：configuration: Cypher regressions in main since v1.1.4: MATCH+CREATE relationship-only and SET clause parsing

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Cypher regressions in main since v1.1.4: MATCH+CREATE relationship-only and SET clause parsing
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Cypher regressions in main since v1.1.4: MATCH+CREATE relationship-only and SET clause parsing
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/192 | Cypher regressions in main since v1.1.4: MATCH+CREATE relationship-only and SET clause parsing

## 16. 配置坑 · 失败模式：configuration: Docs: async_writes yaml examples in README + configuration.md don't match config.go (env-only)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Docs: async_writes yaml examples in README + configuration.md don't match config.go (env-only)
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Docs: async_writes yaml examples in README + configuration.md don't match config.go (env-only)
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/215 | Docs: async_writes yaml examples in README + configuration.md don't match config.go (env-only)

## 17. 配置坑 · 失败模式：configuration: Multiple Cypher correctness bugs: OPTIONAL MATCH, CONTAINS quoting, elementId parameters, wri...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Multiple Cypher correctness bugs: OPTIONAL MATCH, CONTAINS quoting, elementId parameters, write counters, RETURN after writes
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Multiple Cypher correctness bugs: OPTIONAL MATCH, CONTAINS quoting, elementId parameters, write counters, RETURN after writes
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/191 | Multiple Cypher correctness bugs: OPTIONAL MATCH, CONTAINS quoting, elementId parameters, write counters, RETURN after writes

## 18. 配置坑 · 失败模式：configuration: UNWIND $list AS name returns variable name as string literal instead of iterating list (Bolt,...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: UNWIND $list AS name returns variable name as string literal instead of iterating list (Bolt, v1.1.4)
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: UNWIND $list AS name returns variable name as string literal instead of iterating list (Bolt, v1.1.4)
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/189 | UNWIND $list AS name returns variable name as string literal instead of iterating list (Bolt, v1.1.4)

## 19. 配置坑 · 失败模式：configuration: Vector search substrate not updated on runtime writes (external vectors, EMBEDDING_ENABLED=fa...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: Vector search substrate not updated on runtime writes (external vectors, EMBEDDING_ENABLED=false) — stale until restart; degrades resolution during ingest
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: Vector search substrate not updated on runtime writes (external vectors, EMBEDDING_ENABLED=false) — stale until restart; degrades resolution during ingest
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/220 | Vector search substrate not updated on runtime writes (external vectors, EMBEDDING_ENABLED=false) — stale until restart; degrades resolution during ingest

## 20. 配置坑 · 失败模式：configuration: [BUG] Cypher correctness (v1.1.5): `SET x = <map>` replacement drops properties; `SET += <UNW...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: [BUG] Cypher correctness (v1.1.5): `SET x = <map>` replacement drops properties; `SET += <UNWIND alias>`, dynamic labels, and `db.create.setNodeVectorProperty` broken
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: [BUG] Cypher correctness (v1.1.5): `SET x = <map>` replacement drops properties; `SET += <UNWIND alias>`, dynamic labels, and `db.create.setNodeVectorProperty` broken
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/213 | [BUG] Cypher correctness (v1.1.5): `SET x = <map>` replacement drops properties; `SET += <UNWIND alias>`, dynamic labels, and `db.create.setNodeVectorProperty` broken

## 21. 配置坑 · 失败模式：configuration: [BUG] db.index.vector.queryRelationships returns 0 rows on v1.1.7 (node path works)

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: [BUG] db.index.vector.queryRelationships returns 0 rows on v1.1.7 (node path works)
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: [BUG] db.index.vector.queryRelationships returns 0 rows on v1.1.7 (node path works)
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/219 | [BUG] db.index.vector.queryRelationships returns 0 rows on v1.1.7 (node path works)

## 22. 配置坑 · 失败模式：configuration: [Feature] Neo4j drop-in compatibility: accept the default "neo4j" database name and the 3-arg...

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: [Feature] Neo4j drop-in compatibility: accept the default "neo4j" database name and the 3-arg fulltext procedure form
- 对用户的影响：Developers may misconfigure credentials, environment, or host setup: [Feature] Neo4j drop-in compatibility: accept the default "neo4j" database name and the 3-arg fulltext procedure form
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/214 | [Feature] Neo4j drop-in compatibility: accept the default "neo4j" database name and the 3-arg fulltext procedure form

## 23. 配置坑 · 失败模式：configuration: v1.1.4 - Barracuda

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v1.1.4 - Barracuda
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.4 - Barracuda
- 证据：failure_mode_cluster:github_release | https://github.com/orneryd/NornicDB/releases/tag/v1.1.4 | v1.1.4 - Barracuda

## 24. 配置坑 · 失败模式：configuration: v1.1.6 - Cherry Bomb

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this configuration risk before relying on the project: v1.1.6 - Cherry Bomb
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.6 - Cherry Bomb
- 证据：failure_mode_cluster:github_release | https://github.com/orneryd/NornicDB/releases/tag/v1.1.6 | v1.1.6 - Cherry Bomb

## 25. 能力坑 · 能力判断依赖假设

- 严重度：medium
- 证据强度：source_linked
- 发现：README/documentation is current enough for a first validation pass.
- 对用户的影响：假设不成立时，用户拿不到承诺的能力。
- 证据：capability.assumptions | https://github.com/orneryd/NornicDB | README/documentation is current enough for a first validation pass.

## 26. 维护坑 · 失败模式：migration: SET silently fails on nodes that existed before v0→v2 storage migration

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: SET silently fails on nodes that existed before v0→v2 storage migration
- 对用户的影响：Developers may hit a documented source-backed failure mode: SET silently fails on nodes that existed before v0→v2 storage migration
- 证据：failure_mode_cluster:github_issue | https://github.com/orneryd/NornicDB/issues/190 | SET silently fails on nodes that existed before v0→v2 storage migration

## 27. 维护坑 · 失败模式：migration: v1.1.1 - Santeria

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: v1.1.1 - Santeria
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.1 - Santeria
- 证据：failure_mode_cluster:github_release | https://github.com/orneryd/NornicDB/releases/tag/v1.1.1 | v1.1.1 - Santeria

## 28. 维护坑 · 失败模式：migration: v1.1.2 - Purple Haze

- 严重度：medium
- 证据强度：source_linked
- 发现：Developers should check this migration risk before relying on the project: v1.1.2 - Purple Haze
- 对用户的影响：Upgrade or migration may change expected behavior: v1.1.2 - Purple Haze
- 证据：failure_mode_cluster:github_release | https://github.com/orneryd/NornicDB/releases/tag/v1.1.2 | v1.1.2 - Purple Haze

## 29. 维护坑 · 维护活跃度未知

- 严重度：medium
- 证据强度：source_linked
- 发现：未记录 last_activity_observed。
- 对用户的影响：新项目、停更项目和活跃项目会被混在一起，推荐信任度下降。
- 证据：evidence.maintainer_signals | https://github.com/orneryd/NornicDB | last_activity_observed missing

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 证据：downstream_validation.risk_items | https://github.com/orneryd/NornicDB | no_demo; severity=medium

## 31. 安全/权限坑 · 存在评分风险

- 严重度：medium
- 证据强度：source_linked
- 发现：no_demo
- 对用户的影响：风险会影响是否适合普通用户安装。
- 证据：risks.scoring_risks | https://github.com/orneryd/NornicDB | no_demo; severity=medium

## 32. 安全/权限坑 · 来源证据：Cypher regressions in main since v1.1.4: MATCH+CREATE relationship-only and SET clause parsing

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Cypher regressions in main since v1.1.4: MATCH+CREATE relationship-only and SET clause parsing
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/192 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 33. 安全/权限坑 · 来源证据：Multiple Cypher correctness bugs: OPTIONAL MATCH, CONTAINS quoting, elementId parameters, write counters, RETURN after…

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：Multiple Cypher correctness bugs: OPTIONAL MATCH, CONTAINS quoting, elementId parameters, write counters, RETURN after writes
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/191 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 34. 安全/权限坑 · 来源证据：UNWIND $list AS name returns variable name as string literal instead of iterating list (Bolt, v1.1.4)

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：UNWIND $list AS name returns variable name as string literal instead of iterating list (Bolt, v1.1.4)
- 对用户的影响：可能影响授权、密钥配置或安全边界。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/189 | 来源讨论提到 node 相关条件，需在安装/试用前复核。

## 35. 安全/权限坑 · 来源证据：[BUG] Cypher correctness (v1.1.5): `SET x = <map>` replacement drops properties; `SET += <UNWIND alias>`, dynamic label…

- 严重度：medium
- 证据强度：source_linked
- 发现：GitHub 社区证据显示该项目存在一个安全/权限相关的待验证问题：[BUG] Cypher correctness (v1.1.5): `SET x = <map>` replacement drops properties; `SET += <UNWIND alias>`, dynamic labels, and `db.create.setNodeVectorProperty`…
- 对用户的影响：可能影响升级、迁移或版本选择。
- 证据：community_evidence:github | https://github.com/orneryd/NornicDB/issues/213 | 来源讨论提到 python 相关条件，需在安装/试用前复核。

## 36. 维护坑 · issue/PR 响应质量未知

- 严重度：low
- 证据强度：source_linked
- 发现：issue_or_pr_quality=unknown。
- 对用户的影响：用户无法判断遇到问题后是否有人维护。
- 证据：evidence.maintainer_signals | https://github.com/orneryd/NornicDB | issue_or_pr_quality=unknown

## 37. 维护坑 · 发布节奏不明确

- 严重度：low
- 证据强度：source_linked
- 发现：release_recency=unknown。
- 对用户的影响：安装命令和文档可能落后于代码，用户踩坑概率升高。
- 证据：evidence.maintainer_signals | https://github.com/orneryd/NornicDB | release_recency=unknown