[hibernate-issues] [Hibernate-JIRA] Resolved: (HSEARCH-216) Delete by Term when possible

[Emmanuel Bernard (JIRA)]

     [ http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bernard resolved HSEARCH-216.
--------------------------------------

    Resolution: Duplicate

Dupe of HSEARCH-225

> Delete by Term when possible
> ----------------------------
>
>                 Key: HSEARCH-216
>                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-216
>             Project: Hibernate Search
>          Issue Type: Improvement
>          Components: engine
>            Reporter: Sanne Grinovero
>
> discussed on mail list, in short:
> when we know only one entity type is written to a specific index we could avoid the delete on the dual identifier(entityname, databaseID) which needs an IndexReader, and a query, and iterating on the results;
> a deletion by Term using only database identifier would be enough and should be more efficient.
> Additionally if we detect it's possible to do all the work with an IndexWriter we could skip the IndexReader opening.

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