Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Query Not Returning Expected Results and Returning Zeros #183

Closed
bonesyo opened this issue Jan 25, 2021 · 1 comment
Closed

Query Not Returning Expected Results and Returning Zeros #183

bonesyo opened this issue Jan 25, 2021 · 1 comment

Comments

@bonesyo
Copy link

bonesyo commented Jan 25, 2021

Neo4j Version: 4.2.1
Neo4j Mode: Using Aura on GCP
Driver version: Go driver 4.2.1
Operating System: Using Aura on GCP

Steps to reproduce

I apologize since we can not reproduce this outside of our production DB, which contains sensitive data. We are running a larger query where about half way through the return data, it starts to return all Zeros for the return fields. EDIT: We have found that one of the results is chunked, and that is the result that it is getting corrupted.

Expected behavior

The query should return valid data. When connecting to our DB from the Node driver, and running the same query we get expected results.

Actual behavior

The query returns valid data to a certain point, then begins to return all zeros. We are not seeing anything in the logs.

@voutilad
Copy link

I can reproduce this issue with the following cypher running against Neo4j 4.2.2:

UNWIND [18432, 34143] AS n
  RETURN n, [_ IN range(1, n) | 'w'] AS text, "hello!" as msg

If you run the above, the 2nd record will have garbage null bytes in the middle of the very long array in the "text" field. The "msg" field will also be overwritten with a single "w" value instead of the expected string literal of hello!.

2hdddg pushed a commit to 2hdddg/neo4j-go-driver that referenced this issue Jan 26, 2021
Serious issue that could cause corrupt data in records.
Fixes neo4j#183
2hdddg pushed a commit to 2hdddg/neo4j-go-driver that referenced this issue Jan 26, 2021
Serious issue that could cause corrupt data in records.
Fixes neo4j#183
2hdddg pushed a commit to 2hdddg/neo4j-go-driver that referenced this issue Jan 26, 2021
Serious issue that could cause corrupt data in records.
Fixes neo4j#183
@2hdddg 2hdddg closed this as completed in 34c5cb1 Jan 26, 2021
2hdddg pushed a commit that referenced this issue Jan 26, 2021
Serious issue that could cause corrupt data in records.
Fixes #183
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants