[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-471) Ability to selectively index an entity based on its state
[
https://hibernate.onjira.com/browse/HSEARCH-471?page=com.atlassian.jira.p...
]
Emmanuel Bernard commented on HSEARCH-471:
------------------------------------------
After discussions with Sanne, we have decided to keep the dirty checking optimization
disabled when interceptors are used on a given class.
We have several options to enable it down the road. All based on the interceptor
implementor giving us more information on what state it uses:
- put on the interceptor implementation a @UsesProperties("status")
This will be added to the list of properties to consider inside
DocumentBuilder.isDirty("")
- use a new PropertyUsage interface returning the list of used properties. This interface
could be used for class bridges as well.
Ability to selectively index an entity based on its state
---------------------------------------------------------
Key: HSEARCH-471
URL: https://hibernate.onjira.com/browse/HSEARCH-471
Project: Hibernate Search
Issue Type: New Feature
Components: engine, mapping
Affects Versions: 3.1.1.GA
Reporter: Dobes Vandermeer
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira