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
- ArcadeFilterByTypeStep leaks the underlying type-scan cursor on the vertex branch and on every mid-traversal re-open, because close() only closes a CloseableIterator and the vertex wrapper is a plain Iterator
- ColumnarMetrics leaves per-type/per-property meter series registered after a COLUMNAR index is dropped, until the database is reopened
- fix(#11625): an indexed DATE compares its keys by day, not through epoch milliseconds that overflow
- test: an LSM index answers the extreme values of each scalar type as a scan does (after Neo4j's ExtremeValuesLibrary)
- fix(#11635): under COSINE a vector whose squared norm the float cosine cannot hold is unscorable, like the zero vector
- Studio cytoscape/export e2e tests gate their assertions behind the absence of the in-page error, and two of them never assert the capability they name, so a thrown or missing Studio feature passes green
- e2e-python asyncpg ParameterizedInsert catches the protocol error and re-inserts the row with hard-coded literals, so the test certifies nothing about the parameterized INSERT path it is named for
- The JVM Docker image ships the Bolt wire protocol (arcadedb-bolt) but the Dockerfile does not EXPOSE its port 7687, while it does EXPOSE the other opt-in wire ports and the native Dockerfiles do EXPOSE 7687
- The time-series LINE_PROTOCOL error counter counts failed batches, not failed points, so arcadedb.test.ts.inserted.points.error (and the inserted.points success timer) understate lost/ingested points by up to the 500-point batch size
- openCypher: concurrent MERGE that creates the far end of a relationship from a bound node stores it once per transaction (the #11482 check covers only two existing endpoints)
- Docs
- not yet supported