[
http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-471?pag...
]
Hardy Ferentschik commented on HSEARCH-471:
-------------------------------------------
As Sanne is saying, we could do something similar as with _DynamicBoost_, but I have also
the same question:"How do we detect whether we have to issue a index delete
request?"
Say the _User_ is active and indexed. As long as he is not marked as inactive the index
should be kept in sync. Say we have some class level annotation like
_@IndexInclusionCheck_ where you have to specify an implementation class. If the _User_
becomes inactive it should not be indexed, but also a index delete request should be
issued for the first time the user becomes inactive. After that changes to the user
wouldn't need any Lucene index changes. Of course we could just always issue index
delete requests!?
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
Fix For: 3.3.0
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....
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira