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

apoc.export.cypher.* bug with multiple labels sorted #1366

Closed
conker84 opened this issue Dec 13, 2019 · 0 comments · Fixed by #1367
Closed

apoc.export.cypher.* bug with multiple labels sorted #1366

conker84 opened this issue Dec 13, 2019 · 0 comments · Fixed by #1367

Comments

@conker84
Copy link
Collaborator

Expected Behavior (Mandatory)

Given the provided dataset the expected exported query is:

UNWIND [{name:\"A\", properties:{}}] AS row
CREATE (n:Bar{name: row.name}) SET n += row.properties SET n:Baz;

Actual Behavior (Mandatory)

But we have

UNWIND [{name:"A", _id:20, properties:{}}] AS row
CREATE (n:Bar{name: row.name, `UNIQUE IMPORT ID`: row._id}) SET n += row.properties SET n:Baz;

How to Reproduce the Problem

CALL apoc.export.cypher.query('MATCH (n:Baz) RETURN n', null,{stream: true, format: 'plain'})

Simple Dataset (where it's possibile)

CREATE (n:Bar:Baz{name: 'A'})
conker84 added a commit to conker84/neo4j-apoc-procedures that referenced this issue Dec 13, 2019
conker84 added a commit to conker84/neo4j-apoc-procedures that referenced this issue Dec 13, 2019
conker84 added a commit to conker84/neo4j-apoc-procedures that referenced this issue Dec 13, 2019
JMHReif added a commit that referenced this issue Jan 9, 2020
fixes #1366: apoc.export.cypher.* bug with multiple labels sorted
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.

1 participant