Skip to:
It seems that the Lucene indexes are being created based on theindexed class's assembly version.
If we create a new object, it appears in the search results, but assoon as we recompile the assembly the object is no longer found in thesearch.
Is there an option somewhere to ignore the assembly version? Or isthere some other approach we should be using to avoid this issue?
Using NHibernate.Search 2.0.0.1001 with NHibernate 2.0.0.CR1. Building with Visual Studio 2008.
Released 2.0.1
Fixed r515
This is fixed in the trunk of NHS
It seems that the Lucene indexes are being created based on the
indexed class's assembly version.
If we create a new object, it appears in the search results, but as
soon as we recompile the assembly the object is no longer found in the
search.
Is there an option somewhere to ignore the assembly version? Or is
there some other approach we should be using to avoid this issue?
Using NHibernate.Search 2.0.0.1001 with NHibernate 2.0.0.CR1. Building with Visual Studio 2008.