There are multiple approaches to this which stem from denormalizing the dataset.
-
Embed a list of actor IDs in the movie and have a way to reference back. This could look like this
movie = { name: "Batman", year: 1989, actors: [1,2]}
actorOne = { id: 1, name: "Jack Nicholson", born: 1937 }
actorTwo = { id: 2, name: "Michael Keaton", born: 1951 }
Now you can emit the actors directly from the movie document, and then perform a 2. query to load their details as needed. You can of course do this the other way around as well and include a list of movies in the actor data, depends on what makes more sense to you.
- Embed the whole actor in the movie since actors and movies are closely related it can be useful to always query them as one Document, and therefor embed all the information about the actor inside the JSON movie = { name: "Batman", year: 1989, actors: [{ name: "Jack Nicholson", born: 1937 }, { name: "Michael Keaton", born: 1951 }] } This only makes sense for closely related information and can cause trouble if you need to update an actor or want to generate a list of movies an actor has been part of, but this could maybe achieved via a view.
Those would be the options which come to mind, otherwise you would have to know the ID of the batman movie to emit only actors with this id in them, which would be complicated since you would need to query the movie to get it’s id and then generate a view from there to have it’s ID ready. This would also take quite some time and you don’t want to generate and extensive amount of views for every movie in this case.