jexp / neo4j-shell-tools

A bunch of import/export tools for the neo4j-shell
288 stars 55 forks source link

Does "Message: An invalid XML character (Unicode: 0x7)" ring a Bell ? #92

Open unrealwill opened 8 years ago

unrealwill commented 8 years ago

Hello, export work fine but upon import I get this error. "Message: An invalid XML character (Unicode: 0x7)" This is an edge case, but it breaks import at the row : 31914883 after a few hours. The problematic entry was exported as

<node id="n32492192" labels=":Claim:String"><data key="labels">:Claim:String</data><data key="id">q815674$d97daa5b-4894-6754-72d6-ff8625fc132f</data><data key="value">^G</data></node>

This character is not properly escaped into a Unicode character.

For info : the problematic entry is referring to the statement Unicode_character of https://www.wikidata.org/wiki/Q815674

As of now I solved by deleting the problematic entry in my base before reexporting. Let's hope there are no other problematic characters.

Thank you I have ringed the bell :) Will PS: can the person solving this issue also correct it in branch 3.0.0 ty

jexp commented 8 years ago

Where did you get the data from :)

Hmm I thought the XML exporter took care of such unicode characters.

Am 02.06.2016 um 12:46 schrieb unrealwill notifications@github.com:

Hello, export work fine but upon import I get this error. "Message: An invalid XML character (Unicode: 0x7)" This is an edge case, but it breaks import at the row : 31914883 after a few hours. The problematic entry was exported as

:Claim:Stringq815674$d97daa5b-4894-6754-72d6-ff8625fc132f^G

This character is not properly escaped into a Unicode character.

For info : the problematic entry is referring to the statement Unicode_character of https://www.wikidata.org/wiki/Q815674

As of now I solved by deleting the problematic entry in my base before reexporting. Let's hope there are no other problematic characters.

Thank you I have ringed the bell :) Will PS: can the person solving this issue also correct it in branch 3.0.0 ty

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.