Open schivmeister opened 1 year ago
Did anyone manage to reproduce this? What could be the cause for this behavior? Can someone confirm that this is a bug (perhaps a regression)?
Dear developers, Is there any chance that you can look at this problem in the near future? We would like to know if this is indeed a bug, and if yes, is it going to be fixed or not. Thank you!
Hi all,
I can confirm this is a bug. A minimal (YARRRML) example attached for reproducibility: join-on-parent-list.zip.
I'm assuming the problem is that the join operator doesn't take parent lists into account, and perhaps just compares the toString
representation of the parent (so that list) with the child.
I'll put it on our todolist, but our development efforts are guided by projects, so I can't promise a swift handling. If you would need some more timely assistance, we can always discuss further via info@rml.io
Environment
rmlmapper v6.2.2 (reproducible also as far back as v6.1.3 and even older) Linux/WSL2 Java 11
Problem
Given the following kind of input XML:
and the following kind of subject mapping:
and the following kind of predicate-object mapping:
with the following kind of value mapping vocabulary in
JSON
format:Actual
Results in no mapping created for
epo:hasNutsCode
.Expected
Should result in as many instances of
epo:hasNutsCode
with values as there areNUTS
elements withCODE
values, matching terms in the given vocabularynuts.json
.Workaround
Removing all but one
NUTS
element results in a successful mapping ofepo:hasNutsCode
.Input:
Output:
MWE
rml-mwe-nuts-json.zip
Context
This was discovered while troubleshooting #226, a result reproducibility issue pertaining to the mapping of OP TED XML notices to generate RDF.
P.S: The issue described in #226 for reproduction actually is about a partial, incomplete original result, i.e. multiple values created only one mapping, which is no longer reproducible (as in turn evidenced in this ticket).