|
|
bq. I think whatever the generated SQL query is, it would be reasonable to patch the Hibernate Search code to not load all entries in a single batch, but split them up in blocks of some parameter N. I guess it would be easy for you to patch this in Search and verify: propose a new method to set the option and send a patch proposal.
But just like batch loading of collections, this sounds like it would imply multiple round trips to the database. Perhaps in some cases, multiple round trips make sense, but I'm not convinced that this is one of those situations.
One of our driving factors that lead us to search in the first place was speed and performance. Your proposal of a batch fetch would mean we'd need to set the batch size to something such as 25 or 50, resulting between 5 to 10 database queries in order to optimize the performance. In either case, we'd still be looking at such a that solution being would be about 3x- 5x as slow as the proposed ORM modification for {{supportMultiColumnInMarshalledAsExistsWithSubqueryValues}} shown above.
|
|
|
|
|
|
|
|
