It doesn’t seem that map.merge is working with nested maps. How should we do the merge when our maps are looking like this: { "kpiMap": { "KPI613": { "RT1167": 0, "CH1010280": 81200911, "CH1024141": 339799 }, "KPI608": { "RT1167": 0, "CH1010280": 1613843…

I assume you mean merging two maps that look somewhat like that :no_bell:

For this example I am setting up a record with two bins (a, b), each containing a map similar to the one you’ve shown. Only one of the fields exists in both (KPI613): aql> select * from test.demo where PK ='1' +----------------------------------------------------------------------------------------…

Thanks a lot Ronen for the provided solution. I changed my code and put the map.merge into a separate function which I call recursively when the type of v1 and v2 are equal to the metatable for type map (same as your code). This seems to be working, at least I don’t get an error message any longer. …

In general, the purpose of your mapper should be to transform data from what you have in the bins of the record to a smaller data set, for example a map. Get rid of the bin data you’re not interested in, and transform anything else. The purpose of your reducer is to combine similar data coming out o…

I also shared with you a reproducible example via Dropbox. You can use it with the same data dump that I did send previously. Just register the additional UDF calculateOthers.lua and execute the aggregation of the enclosed aql command. Also included is a JSON dump of the corresponding data (SG3.j…

I’ve now replaced the map.merge with a custom routine to loop through the entire map and sum up values manually. The result is actually exactly the same as for the map.merge. I figured out that for some reason only half of the data makes it into the reduce method at all. So in my example the filter…

Depending on your cluster size and the hardware of each node, you probably have multiple mappers running in parallel, each taking on a portion of the records matched by the query. The reducers don’t get records, they get maps which are the output of the mapper. Only filters and mappers have a record…

It’s a single instance that I’m using for developments, but nevertheless I would expect that the reducer sees the same amount of data as the mapper. The result that I’m getting matches the four results I do see in the reducer, hence I assume that the other data is lost somehow. I did provide data …

Ronen, were you able to download the data? Thanks

Sorry about the delay, I had to push out the new Python 1.0.53 release . I’ll get to this soon.

Map.merge doesn't work with nested maps [Resolved]

Client Libraries Python Client

rbotzer November 7, 2019, 5:05pm 15

See

Topic		Replies	Views
UDF problem with maps	3	1227	March 14, 2022
Map Reduce for records using udf against String key and double value User Defined Functions (UDF)	8	3003	October 20, 2014
Atomic increment for nested map Java Client	11	2052	January 26, 2021
Nested map read/get API Data Types query	1	3025	November 7, 2019
About nested Map in a Map value still can be sorted by key	1	1894	November 7, 2019

Map.merge doesn't work with nested maps [Resolved]

Related topics