[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-471) Ability to selectively index an entity based on its state

[Emmanuel Bernard (JIRA)]

    [ https://hibernate.onjira.com/browse/HSEARCH-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45682#comment-45682 ] 

Emmanuel Bernard commented on HSEARCH-471:
------------------------------------------

Another problem is that because we exclude non indexed fields and don't trigger a Work event in this case, we need to force the user to index all the fields that will possibly involve the soft delete logic even if the field is not meant to be indexed int he first place.

An alternative is to list the fields that ought to force a Work trigger. Ideas?

> 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