| I'm confused on two things:
- which library is responsible for the warning? Search is not aware of the OGM dialects and persistence strategies.
- why issue a warning? If the underlying datastore doesn't support multi-fetch, then the user doesn't really have options to improve the loading.
The fact that Search uses the ORM multi-load is just a clean API expressing our need to load all those entities, what happens beyond the API invocation is up to the persister. It's one of those cases in which I'd prefer a clean abstraction and not have Search meddle with specific knowledge of the implementation, unless there's a clear performance benefit of doing differently but I see no possible advantage in not using the multi-load: as far as I know both ORM and OGM are supposed to "fall back" to the most sensible (and efficient) strategies? |