Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
1 Solution
Accepted Solutions
ok, let start from the end
The similar problem present with many API systems, and each have different solution (later), but finally, for extract proper information, You must use proper JSON Path:
where (String)globalMap.get("v_key") it is Your ID
as You can see - we make a loop for all possible ID, than use each value as query parameter on next steps
and final result - as expected
This is was The end of story ... How to fetch this list of ID? it always different
Some systems like Google FireBase where I meet this problem first time have special query parameter "shallow" which return on list of Keys
I not familiar with Mavelink, so You need read how to request only ID from workspace
Or You need write custom routine to do this from file.
The similar problem present with many API systems, and each have different solution (later), but finally, for extract proper information, You must use proper JSON Path:
where (String)globalMap.get("v_key") it is Your ID
as You can see - we make a loop for all possible ID, than use each value as query parameter on next steps
and final result - as expected
This is was The end of story ... How to fetch this list of ID? it always different
Some systems like Google FireBase where I meet this problem first time have special query parameter "shallow" which return on list of Keys
I not familiar with Mavelink, so You need read how to request only ID from workspace
Or You need write custom routine to do this from file.
I think You need attach some pictures of Your Job, and provide little more information about API
If Your API return to You element as array and You extract JSON by JSONPath - You must use (where xxx - number in array)
some time more easy trick - remove by replaceAll [] and than use tNormalize
the benefits - no loops, do not need know size of array
If Your API return to You element as array and You extract JSON by JSONPath - You must use (where xxx - number in array)
some time more easy trick - remove by replaceAll [] and than use tNormalize
the benefits - no loops, do not need know size of array
It very easy - edit You post unless You will see pictures
In other cases - no way to help You
In other cases - no way to help You
ok, let start from the end
The similar problem present with many API systems, and each have different solution (later), but finally, for extract proper information, You must use proper JSON Path:
where (String)globalMap.get("v_key") it is Your ID
as You can see - we make a loop for all possible ID, than use each value as query parameter on next steps
and final result - as expected
This is was The end of story ... How to fetch this list of ID? it always different
Some systems like Google FireBase where I meet this problem first time have special query parameter "shallow" which return on list of Keys
I not familiar with Mavelink, so You need read how to request only ID from workspace
Or You need write custom routine to do this from file.
The similar problem present with many API systems, and each have different solution (later), but finally, for extract proper information, You must use proper JSON Path:
where (String)globalMap.get("v_key") it is Your ID
as You can see - we make a loop for all possible ID, than use each value as query parameter on next steps
and final result - as expected
This is was The end of story ... How to fetch this list of ID? it always different
Some systems like Google FireBase where I meet this problem first time have special query parameter "shallow" which return on list of Keys
I not familiar with Mavelink, so You need read how to request only ID from workspace
Or You need write custom routine to do this from file.
as additional post:
all described above, because in JOSN not included proper id - no any chances to extract Key Name from Talend
all other columns You can extract more easy:
but because id - it is not correct, some other system include _id in JSON body with unique name and all work fine
as example - they own docs, they have id in JSON body, so may be it just Yours error when copy, if all id different, result will be correct
and my first post related to normalise, was about array constructions similar to:
and again if You proper copy JSON, You can extract id list from Results:
it is from documentation web page, but not from Your example
all described above, because in JOSN not included proper id - no any chances to extract Key Name from Talend
all other columns You can extract more easy:
but because id - it is not correct, some other system include _id in JSON body with unique name and all work fine
as example - they own docs, they have id in JSON body, so may be it just Yours error when copy, if all id different, result will be correct
and my first post related to normalise, was about array constructions similar to:
"results":
}
and again if You proper copy JSON, You can extract id list from Results:
it is from documentation web page, but not from Your example