[hibernate-issues] [Hibernate-JIRA] Closed: (HSEARCH-182) Use Directory getLockID() to uniquely identify a directory provider
Sanne Grinovero (JIRA)
noreply at atlassian.com
Sat Feb 11 18:18:13 EST 2012
[ https://hibernate.onjira.com/browse/HSEARCH-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanne Grinovero closed HSEARCH-182.
-----------------------------------
Resolution: Out of Date
Since introduction of IndexManager this doesn't apply, equals/hashcode are not needed.
> Use Directory getLockID() to uniquely identify a directory provider
> -------------------------------------------------------------------
>
> Key: HSEARCH-182
> URL: https://hibernate.onjira.com/browse/HSEARCH-182
> Project: Hibernate Search
> Issue Type: Improvement
> Components: directory provider
> Reporter: Emmanuel Bernard
> Priority: Minor
>
> Today the DirectoryProvider needs to implement equals and hashCode so that the underlying Directory is unique.
> We could delegate that to the directory.getLockID() which seem to fulfill the same contract.
> Not sure it works well with our lazy initialization strategy though. This needs to be checked out.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the hibernate-issues
mailing list