In-memory lookup workaround
Hello all,
I faced with issue with in-memory lookup. According to snaplogic documentation, [https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1439008/In-Memory+Lookup] it does not supported structured JSON path like '$customer.address. It can work only with values like $customer.
Even if I put mapper before the lookup snap, it doesn’t work.
I have following json document
[{
“Item”: {
“date”: “9999-12-31T00:00:00.000Z”,
“GeoArray”: [
{
“GeographyName”: {
“GeographyDescription”: “N\A”,
“GeographyStateID”: 505074
},
“@key”: “1753-01-01 00:00:00.000000;505074;1;1;404500”
}
]
}
}]
where geography state is id based on which description should be taken from vocabulary which is stored in separate file like key value pairs.
Basically I need to get following json as a desired result
[{
“Item”: {
“date”: “9999-12-31T00:00:00.000Z”,
“GeoArray”: [
{
“GeographyName”: {
“GeographyDescription”: “N\A”,
“GeographyStateID”: 505074,
“GeographyStateDescription”: “Utah”
},
“@key”: “1753-01-01 00:00:00.000000;505074;1;1;404500”
}
]
}
}]
Does anybody has any idea how to implement it?
I appreciate any help
Hi,
Please check the attached pipeline, that uses a mapper to workaround the limitation of in memory snap
InMemory_2019_10_03.slp (10.3 KB)
