arcadedb
https://github.com/arcadedata/arcadedb
Triage Issues!
When you volunteer to triage issues, you'll receive an email each day with a link to an open issue that needs help in this project. You'll also receive instructions on how to triage issues.
Triage Docs!
Receive a documented method or class from your favorite GitHub repos in your inbox every day. If you're really pro, receive undocumented methods or classes and supercharge your commit history.
not yet supported0 Subscribers
Add a CodeTriage badge to arcadedb
Help out
- Issues
- Traversing a vertex's edges during concurrent edge deletes fails with RecordNotFoundException (EdgeAppendMergeRaceTest fails about half the time)
- gRPC: a vector is one GrpcValue per element, with no packed float array; 15 x 768 floats cost 7.3 ms to build on the client against 0.18 ms packed
- openCypher: MATCH (a {key: $k})-[r]->(b) WHERE b.key IN $list walks every relationship of a; with a UNIQUE key the far end could be sought per element (80,000 relationships: 344 ms for 200 keys, 32 ms for 1)
- fix(#11688): openCypher DETACH DELETE marks the relationships bound in the row that it removes with their endpoint as deleted
- IMPORT DATABASE over HTTP holds the whole import in one transaction: 40,000 full-text-indexed documents take 2.2 GB of live heap or run a 3 GB server out of memory, against 289 MB with autoCommit false
- IMPORT DATABASE of an ArcadeDB export named without .jsonl (backup.tgz) imports one Document from the header line and reports OK, dropping every record
- Untyped LIST with a BY ITEM index: CONTAINS answers differently with and without the index when a list holds a nested list
- TRUNCATE TYPE racing concurrent INSERT and DELETE fails with RecordNotFoundException (HTTP 404) for a record another transaction deleted, instead of skipping it or raising a retryable conflict
- Concurrent UPDATE and DELETE of the same records leave NOTUNIQUE index entries for deleted records; after RID reuse an indexed lookup returns a row with another value, and CHECK DATABASE reports nothing
- CHECK DATABASE does not compare index entries with records: entries for deleted records, or with a key the record does not hold, pass as healthy and FIX leaves them
- Docs
- not yet supported