[hibernate-issues] [Hibernate-JIRA] Commented: (HSEARCH-225) Avoid using IndexReader.deleteDocument when index is not shared amongst several entity types

[Hardy Ferentschik (JIRA)]

    [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_30650 ] 

Hardy Ferentschik commented on HSEARCH-225:
-------------------------------------------

Would it be worth to defer this issue until release 2.4 of Lucene. As mentioned on the dev-list, we could then use IndexWriter.deleteDocuments(Query query). Would this not be a better and cleaner solution which would address all our needs?

Here is the Lucene Jira issue regarding IndexWriter.deleteDocuments(Query query): https://issues.apache.org/jira/browse/LUCENE-1194



> Avoid using IndexReader.deleteDocument when index is not shared amongst several entity types
> --------------------------------------------------------------------------------------------
>
>                 Key: HSEARCH-225
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-225
>             Project: Hibernate Search
>          Issue Type: Bug
>            Reporter: Emmanuel Bernard
>            Assignee: Hardy Ferentschik
>             Fix For: 3.1.0.Beta1
>
>
> When an index is not shared amongst several entities (ie only a given class is stored in the index, we can use IndexWriter.deleteDocuments() using a term pointing to the id. This cannot work for index shared across several entities, even subclasses.
> We need to build a flag in the metadata and compute it when the SearchFactory is built. Then reuse it during the indexing process to enable the optimization

-- 
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