Skip to content

Query fails with error and then starts to just hang from second time #93

@jgupta

Description

@jgupta

Following as an simplified example of query that fails with an error as mentioned below. From second time, it just shows nothing.

CREATE (q:Q{id:'123'})
WITH q
OPTIONAL MATCH (e:E{id: '456'})
MERGE (e)<-[:TAGGED]-(q)
RETURN e,q;
ERROR Client triggered an unexpected error [Neo.DatabaseError.General.UnknownError]: Access to record Node[-1,used=false,rel=-1,prop=-1,labels=Inline(0x0:[]),light,secondaryUnitId=-1] went out of bounds of the page. The record size is 15 bytes, and the access was at offset -15 bytes into page 0, and the pages have a capacity of 8190 bytes. The mapped store file in question is xxxxxx/neostore.nodestore.db, reference 453e4da6-a9c7-4073-9a1f-25104b79a8e2.

This is happening on all OngDB versions.

Expected output: This query should fail softly as optional match is not found. It should not just get stuck and freeze/hang.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions