This is a straight DB mapper, but we do have a cache based mapper that pulls back the avatar id, since you are using two db mappers in this solution, it seems like you could at least cut down on some of the db load by using the cache mapper.  Take a look at the bean getPersonsByIdsMapper in the Mappers Spring config.