metastar/meta-core
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

v2.0.0: claims model - signed MMUR2 votes in a truth DB, merged view in a rebuildable cache DB; POST /api/claims, claims and merge routes, unsigned writes answer 410
Build and Push Docker Image / build (push) Successful in 5m1s
Details

Browse Source
This commit is contained in:
Worph
2026-10-25 17:36:00 +00:00
parent b0adefb97b
commit 84af298792
78 changed files with 7203 additions and 5617 deletions
Download Patch File Download Diff File Expand all files Collapse all files
tools/search-parity/README.md
+5 -3
View File
@@ -1,21 +1,23 @@
# search-parity
Regression check for `POST /api/metadata/search` against a running meta-core.
Since v2.0.0 it reads the merged view from the cache database
(`/meta-core/db-cache/cache.db`), which keeps the v1 `file:<rid>/<field>` layout.
- `parity.py <meta-core.db>` builds ~230 queries from real records (free text,
- `parity.py <cache.db>` builds ~230 queries from real records (free text,
short tokens, key-set and flat filters, exact/contains, multi-filter). It
computes each query's expected result by brute force: one streaming pass
over every record, using a port of the Go matchers. Then it diffs that
against the live API. Any `lost` result means the SQL candidate superset
dropped a real match.
- `timing.py [meta-core.db]` times the same query set at limit 100 and 2000.
- `timing.py [cache.db]` times the same query set at limit 100 and 2000.
Run them inside the container. It has python3 and reads the database
read-only:
```bash
docker cp tools/search-parity metacore-app:/tmp/sp
docker exec metacore-app python3 -u /tmp/sp/parity.py /meta-core/db/meta-core.db
docker exec metacore-app python3 -u /tmp/sp/parity.py /meta-core/db-cache/cache.db
docker exec metacore-app python3 -u /tmp/sp/timing.py
```