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.

Sign up for GitHub

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

Jump to bottom

Possible bug in apoc graphml export #1449

Closed
nabsabraham opened this issue Mar 17, 2020 · 5 comments · Fixed by #1638
Closed

Possible bug in apoc graphml export #1449

nabsabraham opened this issue Mar 17, 2020 · 5 comments · Fixed by #1638
Assignees
@conker84
Projects
Larus Development

Comments

@nabsabraham
Copy link

I think this is a bug in the apoc.export.graphml.all function. The keys in blue are generated to be the only unique ids but the keys in red for the actual graph use a key named 'labels' that was not generated in the unique id list. This is throwing off a graph viz tool that I am using downstream - how can this be fixed?

image

Tutorial from here.
@jexp
Copy link
Member

jexp commented Mar 19, 2020

Thanks a lot for the report, yes, looks like a bug.

@jexp
Copy link
Member

jexp commented Mar 19, 2020

Currently you can only fix it by editing the file and fixing the <key> entry.

@nabsabraham
Copy link
Author

thanks! I'll wait on your fix :)

@conker84 conker84 added this to Backlog in Larus Development May 14, 2020
@neocsbee
Copy link

I am also facing the same error. It appears to be an issue only with nodes. Haven't come across an issue with edges yet.

image

Along with fixing the entry, is it possible to remove the ":" before the labels?
For example, in the above Football GraphGist case, "Player" and "Team" are labels instead of ":Player" and ":Team".

@jexp: Will follow your tip for fixing the entry in the meantime.

vga91 added a commit to vga91/neo4j-apoc-procedures that referenced this issue Aug 28, 2020
@vga91
fixes neo4j-contrib#1449: Possible bug in apoc graphml export
948cdb9
@vga91 vga91 mentioned this issue Aug 28, 2020
Closed
vga91 added a commit to vga91/neo4j-apoc-procedures that referenced this issue Aug 28, 2020
@vga91
fixes neo4j-contrib#1449: Possible bug in apoc graphml export
78e87a4
@vga91
Copy link
Collaborator

vga91 commented Aug 28, 2020

Hi @nabsabraham, what graph viz tool did you use to test the graph? Thanks.

@vga91 vga91 mentioned this issue Aug 28, 2020
Merged
Larus Development automation moved this from Backlog to Done Sep 24, 2020
mneedham pushed a commit that referenced this issue Sep 24, 2020
@vga91
Fixes #1449: Possible bug in apoc graphml export (#1638)
13f6798 
* fixes #1449: Possible bug in apoc graphml export

* fixes #1449: Possible bug in apoc graphml export
@Basti82b Basti82b mentioned this issue Oct 17, 2020
Closed
mneedham pushed a commit that referenced this issue Nov 13, 2020
@vga91 @mneedham
Fixes #1449: Possible bug in apoc graphml export (#1638)
fa81cde 
* fixes #1449: Possible bug in apoc graphml export

* fixes #1449: Possible bug in apoc graphml export
conker84 pushed a commit to conker84/neo4j-apoc-procedures that referenced this issue Mar 29, 2021
@vga91 @conker84
Fixes neo4j-contrib#1449: Possible bug in apoc graphml export (neo4j-…
9becab0 
…contrib#1638)

* fixes neo4j-contrib#1449: Possible bug in apoc graphml export

* fixes neo4j-contrib#1449: Possible bug in apoc graphml export
conker84 pushed a commit that referenced this issue Apr 12, 2021
@vga91 @conker84
Fixes #1449: Possible bug in apoc graphml export (#1638)
942f812 
* fixes #1449: Possible bug in apoc graphml export

* fixes #1449: Possible bug in apoc graphml export
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@conker84 conker84

Labels
None yet
Projects
Larus Development
  
Done
Milestone
No milestone
5 participants
@jexp @conker84 @neocsbee @vga91 @nabsabraham