EDGE Creation Failure With NullPointer Exception

#1

My first JSON file for etl is:

{
“config”: {
“log”: “debug”
},
“extractor” : {
“jdbc”: { “driver”: “oracle.jdbc.driver.OracleDriver”,
“url”: “",
“userName”: "
”,
“userPassword”: “*”,
“query”: “select * from ref_typ_t” }
},
“transformers” : [
{ “vertex”: { “class”: “REF_TYP_T”} },
],
“loader” : {
“orientdb”: {
“dbURL”: “plocal:/pgDATA/orientdb-3.0.17/databases/glmpoc8g01”,
“dbAutoCreate”: true,
“indexes”: [
{“class”:“REF_TYP_T”, “fields”:[“REF_TYP_ID:integer”], “type”:“UNIQUE” }
]
}
}
}

And my Second JSON file for ETL is:

{
“config”: {
“log”: “debug”
},
“extractor” : {
“jdbc”: { “driver”: “oracle.jdbc.driver.OracleDriver”,
“url”: “",
“userName”: "
”,
“userPassword”: “*”,
“query”: “select * from ref_t” }
},
“transformers” : [
{ “vertex”: { “class”: “REF_T”} },
{ “edge”: { “class”: “has_REF_TYP”, “direction” : “out”, “joinFieldName”: “REF_TYP_ID”,“lookup”:“REF_TYP_T.REF_TYP_ID”, “unresolvedLinkAction”:“CREATE”} }
],
“loader” : {
“orientdb”: {
“dbURL”: “plocal:/pgDATA/orientdb-3.0.17/databases/glmpoc8g01”,
“dbAutoCreate”: true,
“indexes”: [
{“class”:“REF_T”, “fields”:[“REF_ID:integer”], “type”:“UNIQUE” }
]
}
}
}

Without the “edge” clause in the second, the data is loading without any errors but with the edge clause given, I am getting the following error:

OrientDB etl v.3.0.17 - Veloce (build 84af3dc7a5f8bca700354564d5fcc3b7545441fc, branch 3.0.x) https://www.orientdb.com

2019-04-09 09:45:50:144 INFO Detected limit of amount of simultaneously open files is 262144, limit of open files for disk cache will be set to 130560 [ONative]
2019-04-09 09:45:52:575 INFO 540594708480 B/515551 MB/503 GB of physical memory were detected on machine [ONative]
2019-04-09 09:45:52:576 INFO Soft memory limit for this process is set to -1 B/-1 MB/-1 GB [ONative]
2019-04-09 09:45:52:576 INFO Hard memory limit for this process is set to -1 B/-1 MB/-1 GB [ONative]
2019-04-09 09:45:52:577 INFO Path to ‘memory’ cgroup is ‘/’ [ONative]
2019-04-09 09:45:52:580 INFO Mounting path for memory cgroup controller is ‘/sys/fs/cgroup/memory’ [ONative]
2019-04-09 09:45:52:581 INFO cgroup soft memory limit is 9223372036854771712 B/8796093022207 MB/8589934591 GB [ONative]
2019-04-09 09:45:52:582 INFO cgroup hard memory limit is 9223372036854771712 B/8796093022207 MB/8589934591 GB [ONative]
2019-04-09 09:45:52:583 INFO Detected memory limit for current process is 540594708480 B/515551 MB/503 GB [ONative]
2019-04-09 09:45:52:584 INFO JVM can use maximum 7282MB of heap memory [OMemoryAndLocalPaginatedEnginesInitializer]
2019-04-09 09:45:52:584 INFO Because OrientDB is running outside a container 12% of memory will be left unallocated according to the setting ‘memory.leftToOS’ not taking into account heap memory [OMemoryAndLocalPaginatedEnginesInitializer]
2019-04-09 09:45:52:584 INFO OrientDB auto-config DISKCACHE=446,403MB (heap=7,282MB os=515,551MB) [orientechnologies]
2019-04-09 09:45:52:587 INFO System is started under an effective user : orientdb [OEngineLocalPaginated]
2019-04-09 09:45:52:697 INFO WAL maximum segment size is set to 102,019 MB [OrientDBEmbedded]
2019-04-09 09:45:52:724 INFO BEGIN ETL PROCESSOR [OETLProcessor]
2019-04-09 09:45:53:137 INFO Started execution with 1 worker threads [OETLProcessor]
2019-04-09 09:45:53:177 INFO Direct IO for WAL located in /pgDATA/orientdb-3.0.17/databases/glmpoc8g01 is allowed with block size 4096 bytes. [OCASDiskWriteAheadLog]
2019-04-09 09:45:53:177 INFO Page size for WAL located in /pgDATA/orientdb-3.0.17/databases/glmpoc8g01 is set to 4096 bytes. [OCASDiskWriteAheadLog]
2019-04-09 09:45:53:490 INFO Storage ‘plocal:/pgDATA/orientdb-3.0.17/databases/glmpoc8g01’ is opened under OrientDB distribution : 3.0.17 - Veloce (build 84af3dc7a5f8bca700354564d5fcc3b7545441fc, branch 3.0.x) [OLocalPaginatedStorage]
2019-04-09 09:45:53:726 INFO + extracted 0 records (0 records/sec) - 0 records -> loaded 0 documents (0 documents/sec) Total time: 1000ms [0 warnings, 0 errors] [OETLProcessor]$ANSI{green {db=glmpoc8g01}} Error during edge deletion
java.lang.NullPointerException
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.addEdgeInternal(ODatabaseDocumentAbstract.java:1872)
at com.orientechnologies.orient.core.db.document.ODatabaseDocumentAbstract.newEdge(ODatabaseDocumentAbstract.java:1754)
at com.orientechnologies.orient.core.record.impl.OVertexDelegate.addEdge(OVertexDelegate.java:258)
at com.orientechnologies.orient.etl.transformer.OETLEdgeTransformer.createEdge(OETLEdgeTransformer.java:223)
at com.orientechnologies.orient.etl.transformer.OETLEdgeTransformer.executeTransform(OETLEdgeTransformer.java:135)
at com.orientechnologies.orient.etl.transformer.OETLAbstractTransformer.transform(OETLAbstractTransformer.java:40)
at com.orientechnologies.orient.etl.OETLPipeline.execute(OETLPipeline.java:93)
at com.orientechnologies.orient.etl.OETLPipelineWorker.run(OETLPipelineWorker.java:42)
at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

2019-04-09 09:45:53:864 SEVER {db=glmpoc8g01} Error in Pipeline execution: java.lang.IllegalArgumentException: source record is not a vertex [OETLPipeline]
2019-04-09 09:45:53:865 SEVER ETL process has problem: [OETLProcessor]
2019-04-09 09:45:54:041 INFO END ETL PROCESSOR [OETLProcessor]
2019-04-09 09:45:54:042 INFO + extracted 77 records (243 records/sec) - 77 records -> loaded 0 documents (0 documents/sec) Total time: 1316ms [0 warnings, 1 errors] [OETLProcessor]
2019-04-09 09:45:54:043 INFO Orient Engine is shutting down… [Orient]

I am using the community version on Linux.
Kindly help me in understanding what is the problem in this scenario.

0 Likes