[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-471) Ability to selectively index an entity based on its state
Sanne Grinovero (JIRA)
noreply at atlassian.com
Fri Apr 9 13:21:59 EDT 2010
[ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36346#action_36346 ]
Sanne Grinovero commented on HSEARCH-471:
-----------------------------------------
+1 on this, it's not an unusual question on forums either.
the searches won't be speeded up much, but surely some memory is spared and some index changes too (avoid the insert/update work), which in turn makes cached filters possibly live longer, etc..
what about something similar to @DynamicBoost ?
how will we detect if an entity changed from "indexed" to "nonindexed"? it should be deleted from index in that case.
> Ability to selectively index an entity based on its state
> ---------------------------------------------------------
>
> Key: HSEARCH-471
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-471
> Project: Hibernate Search
> Issue Type: New Feature
> Components: mapping
> Affects Versions: 3.1.1.GA
> Reporter: Dobes Vandermeer
> Priority: Minor
>
> In our system we have entities that are searched but not all of them are available for search - some of them are flagged as "removed". It would improve the efficiency of our search subsystem if we could implement a kind of "filter" that blocked these entities from being added to the search index, since we wouldn't have to make that a search term and our indexes would be somewhat smaller.
--
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.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list