I've encountered some strange behaviour in Compass 1.2.2 (and 1.2.1 I guess).
We have a Compass/Hibernate applications. Hibernate does the primary storage, Compass - full text indexing, via GPS.
A while ago our users started complaining that too few results are found. But when the administrator executes a full reindex (it's done via GPS), the records start getting found again - until they're resaved.
After some hours of research I've found out the following.
We have an OSEM model with mappings generated from the XML Schema. We typically generate properties as follows:
We've got the meta-data/@store='no' here. I've tried switching meta-data/@store='no' to 'yes' and surprizingly properties start to work (i.e. being found) again.
So at the moment I changed store to 'yes' everywhere. Still not sure that this was the correct way to address the situation.
Is there maybe some obvious error that I'm missing?
I thought properties are searchable (indexed) even if store is 'no'. I'm even allright if the properties with meta-data/@store='no' are not searchable/indexed but what surprizes me is that these properties ARE searchable after the full reindex (SpringHibernate3Device.index()).
I agree, this is strange... . When you set things to store="no", then it should be indexed and searchable (but, you won't be able to read them back). Is there a chance that you can produce a simple test case? If possible, similar to what Compass has in its tests module (or even within it) - this will speed things up.