[ http://opensource.atl
assian.com/projects/hibernate/browse/HSEARCH-34?page=com.atl
assian.jira.plugin.system.issuetabpanels:comment-tabpanel#ac
tion_26718 ]
Vladislav Nikitin commented on HSEARCH-34:
------------------------------------------
Lazy load of query result will be extreemly useful for me
too.
Here is my use case:
I'm working on the application (Hibernate based), wich
contains a lot of users profiles. I need to implement a web
service, which performs searching for information of one or
more profiles using some criteria and I want to improve the
performance using indexing in Hibernate Search.
Most often criterias are "First Name =",
"Last Name =", "Middle Name =",
"Login Name =" or their combinations. Actually,
this information is all, I need to return... So, my idea is
to make them stored and avoid hitting the database.
I expected, that fields, which are annotatated as Store.YES
are taken from the Lucene indices, but Hibernate Search
always queries the database for each object, from search
result (actually one query per object). So, I expect
significant lack of performance in this case. But lazy
initialization of fullTextQuery results will work for me
pretty good.
BTW: I'm not care if the stored fields may be slightly
expired, because I plan to use schduled update of indices.
Probably it should be possible to create fullTextQuery with
or without lazy initialization... Probably as an additional
parameter lazyLoad = true/false in createFullTextQuery()
> Lazy load the query results
> ---------------------------
>
> Key: HSEARCH-34
> URL: http://opensource.atlassian.com/projects/hib
ernate/browse/HSEARCH-34
> Project: Hibernate Search
> Issue Type: Improvement
> Components: query
> Affects Versions: 3.0.0.beta2
> Reporter: Behrang Javaherian
>
> Search operation should not have any database hit until
required. So the search result should be a list of entities
with their id and all Store.YES or Store.Compress fields are
loaded, accessing any other field should cause database hit.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the
administrators: http://opensource.atlassian.com/pro
jects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atl
assian.com/software/jira
_______________________________________________
hibernate-issues mailing list
hibernate-issues lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-issu
es
|
