-
Notifications
You must be signed in to change notification settings - Fork 872
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.
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
[MERGE]Stop working in odb214 #5158
Comments
From @simper66 on October 19, 2015 8:57 By the way, the MERGE block: {"merge": { "log": "DEBUG", "joinFieldName":"geoNameId", "lookup":"LocationUIDS_IDX_TMP", "unresolvedLinkAction":"SKIP"}}, |
Could you provide a full json configuration and a small set of data. If you can provide a query that confirm it isn't working, it would be the best. |
From @simper66 on October 19, 2015 11:0 Hi Rob, I simplified as much of possible and able to execute with same issue. DATABASE SCRIPT: CREATE DATABASE remote:192.168.16.72:2424/xLocation root qaz plocal graph; CREATE CLASS Location EXTENDS V; CREATE CLASS Country EXTENDS Location; CREATE VERTEX Location SET geoNameId = 2510769 ETL SCRIPT: {
} DATA: ES ESP 724 SP Spain Madrid 504782 46505963 EU .es EUR Euro 34 ##### ^(\d{5})$ es-ES,ca,gl,eu,oc 2510769 AD,PT,GI,FR,MA WARN: All is a single line and there is one last TAB in the data line. MERGE OUTPUT: [0:merge] DEBUG Transformer input: {geoNameISO:ES,geoNameISO3:ESP,geoNameISONumeric:724,geoNameFips:SP,geoNameCountry:Spain,geoNameCapital:Madrid,geoNameArea:504782,geoNamePopulation:null,geoNameContinent:EU,geoNameTld:.es,geoNameCurrencyCode:EUR,geoNameCurrencyName:Euro,geoNamePhone:34,geoNamePostalCodeFormat:#####,geoNamePostalCodeRegex:^(\d{5})$,geoNameLanguages:es-ES,ca,gl,eu,oc,geoNameId:2510769,geoNameNeighbours:AD,PT,GI,FR,MA,geoNameEquivalentFipsCode:null} Don´t know if it is important but note that the class being loaded is different from the lookup target class. The former inherits the latter. In ODB21 the 2 classes are merged and the existing Location vertex is extended and becoming a Country vertex with all the data loaded. |
Thank you very much. I will write a test with this material. |
From @simper66 on October 19, 2015 14:34 I have looked better and i create the "base" vertex with the same class that the "merge" vertex. So, in the DB SCRIPT we can change the last line: CREATE VERTEX Location SET geoNameId = 2510769; It fails anyway... |
I've fixed the problem with the merge Transformer. It will be on next 2.1.7 hot fixe and 2.2. |
From @simper66 on October 19, 2015 8:38
Hi,
I think Merge has stopped working in odb214.
The lookup goes fine but the merge is not being done.
[0:merge] DEBUG Transformer input: {geoNameISO:ES,geoNameISO3:ESP,..........}
[0:merge] DEBUG joinValue=2510, lookupResult=Country#20:0{geoNameId:2510,......} v1
[0:merge] DEBUG Transformer output: null
The output in odb21 works as expected:
[0:merge] DEBUG Transformer input: {geoNameISO:ES,....}
[0:merge] DEBUG joinValue=2510, lookupResult=Country#20:0{geoNameId:2510,...} v1
[0:merge] DEBUG merged record Country#20:0{geoNameId:2510, geoNameISO:ES,...}
[0:merge] DEBUG Transformer output: Country#20:0{geoNameId:2510, geoNameISO:ES,..} v1
Enviroment:
OrientDB: OrientDB 2.1.4 GA Community Edition (October 13, 2015)
SO: Windows7
JDK: Jdk 1.8.0_45
OrientDB Configuration: No special configuration. The one out of the box.
Mode: Standalone. server.bat & oetl.bat
Copied from original issue: orientechnologies/orientdb-etl#101
The text was updated successfully, but these errors were encountered: