[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...
]
Sanne Grinovero commented on HSEARCH-471:
-----------------------------------------
Can't we just have both? I don't mind having my integration code be a couple of
lines more complex.
For Infinispan Query for example I _could_ look at the previous version of a put
operation, if the return value is not being prevented to be loaded by using other options,
and to do something akin to dirty checking (although not the same). It's going to be
up to this integration code to be responsible for this feature to be used, don't you
think that's acceptable?
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