taffyb
November 10, 2021, 10:35am
1
I am following the README at GitHub - neo4j-contrib/osm: OSM Data Model for Neo4j
When I run the command
I get the following error. Can anyone suggest what I have done wrong?
=================================================
Available resources:
IMPORT FAILED in 18941d 10h 16m 21s 624ms.
I tried this out, and it seems one of the internal API's that Neo4j has for arguments processing when doing batch imports has changed slightly. This is rare, but always possible with internal API's. I've rebuilt it with a small change that I copied from the Neo4j 4.2 version I ported earlier this year.
Try the new release at Release OSM 0.2.3-neo4j-4.1.6 · neo4j-contrib/osm · GitHub
taffyb
November 11, 2021, 4:28pm
3
Thanks Craig. However I am sorry to say I pulled down the latest from the repo and rebuilt, but 4.1.6 still gives the same error.
Re-reading your original question, I note that you are getting the failure for the offline import, not actually running the OSM procedures within Neo4j. In this case this is not a compatibility issue, but a missing class issue.
In the README, it says you should run mvn dependency:copy-dependencies before running the command-line import. I just tried the command-line import without that command and got the error:
Error: Unable to initialize main class org.neo4j.gis.osm.OSMImportTool
Caused by: java.lang.NoClassDefFoundError: org/neo4j/io/fs/FileSystemAbstraction
This is not the same error you got. Your run seemed to get further before generating an error. When I copy dependencies, the import succeeds with no error. So I wonder if you perhaps ran the copy-dependencies with a different Neo4j version, and then rebuilt with the desired version, so you got incompatible dependencies?
Could you try repeating the steps:
mvn clean install
mvn dependency:copy-dependencies
java -Xms1024m -Xmx1024m -cp "./target/osm-0.2.3-neo4j-4.1.6.jar;target/dependency/*" org.neo4j.gis.osm.OSMImportTool --skip-duplicate-nodes --delete --into "C:\Users###.Neo4jDesktop\relate-data\dbmss\dbms-853e618d-3f88-4143-bd60-be6406e59b6a" --database map2 ./map.osm
If this still gives the same error, can you provide a listing of the target/dependency directory's contents so I can see what files are there?
taffyb
November 16, 2021, 8:10am
5
Thanks Craig,
I have not had the opportunity to try again yet. However before I do there are a couple of things I would like to check.
" So I wonder if you perhaps ran the copy-dependencies with a different Neo4j version "
I have not been building this on the same machine as my Neo4j instance, does it need to be? I thought that is what maven dependencies was for (retrieving all dependencies from a repro). How do I determine which version the dependencies have been built for. I am using desktop so, can setup whatever version I need.
For reference please find attached the log of "mvn dependencies"
(Attachment dependencies.log is missing)
taffyb
November 16, 2021, 8:14am
6
mvn dependency:copy-dependencies >dependencies.log
[INFO] Scanning for projects...
It is important to run mvn dependency:copy-dependencies on the same computer you plan to run on. This command copies all the libraries needed into the target/dependency directory. If you see the log you sent:
It has copied this file into D:\Work\Equator\OSM\osm\target\dependency\neo4j-4.1.6.jar.
You can run on another computer, but then you need to copy all these JAR files onto that computer, and make sure that the command includes them on the classpath.
Your original command you sent was:
java -Xms1024m -Xmx1024m -cp "./target/osm-0.2.3-neo4j-4.1.3.jar;target/dependency/*" org.neo4j.gis.osm.OSMImportTool --skip-duplicate-nodes --delete --into "C:\Users###.Neo4jDesktop\relate-data\dbmss\dbms-853e618d-3f88-4143-bd60-be6406e59b6a" --database map2 ./map.osm
This means it expected to find all these jars in the target/dependency folder relative to where you ran the command. If the files are not there, then a classpath exception will be thrown.
Can you confirm which files are in that directory on the computer you are running the command? It should be the complete list you sent above.
Hi @craig.taverner - I'm wondering if this error is due to incompatibility with apple's M1 chip. I get this same error when using the OSMImportTool on mac's with the M1 chip, but my same steps work fine on an older mac with the intel chip. Any thoughts / suggestions on making it work with M1? Thanks! - Brian