Ensuring parents are pulled before children

[willtrking]

I'm considering using this river to index data from MySQL which result in parent/child relationships in elasticsearch. Is there a way to ensure that the river which indexes the parent documents runs before the river which indexes the child documents?

One possible solution I had would be to have a script which executes oneshot strategies in the proper order, but I'd like to avoid this if possible.

[jprante]

Thanks for the request.

A future version - based on elasticsearch-gatherer - will be able to support more than one SQL statement per run, that can be executed in order, for example for parent-then-children building.

Note, from the perspective of ES, you do not have to index parent before children, you can mix them.