[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-172?pag...
]
Emmanuel Bernard commented on HSEARCH-172:
------------------------------------------
So let's say you have one million matching elements, Hibernate Search will have to
read one million id, and do a firstResult / maxResult in database in one giant query
requesting all the ids *if* we are in an optimistic situation.
Pessimistic situation (some EAGER collection loading is on the work), we would have to
sort 1 million objects in memory.
I don't see this as a practical solution. But let's try to push the discussion
further.
Add ability to do a Hibernate Sort rather then Lucene Sort
----------------------------------------------------------
Key: HSEARCH-172
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-172
Project: Hibernate Search
Issue Type: Improvement
Components: engine
Reporter: Josh Atir
Priority: Minor
I have a case in which a Lucene sort would be much more expensive then a sql sort. I can
specify a sort order using Criteria, which causes the entity loading query to be sorted
correctly. The engine then ignores the order that was returned, and instead returns the
results based on the order it was received from Lucene.
I'd like the ability to specify a Hibernate sort rather then a Lucene sort.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/hibernate/secure/Administrators....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira