Item11811: MongoDB silently ignores topics which have no _latestIsLoaded
version
Priority: Normal
Current State: Needs Developer
Released In: n/a
Target Release: n/a
I've been using a crusty version of trunk in production for a long time now, so I don't know if this inconsistency arises any more using current code.
However, it would be nice to add this sanity check anyway:
Currently,
./rest /MongoDBPlugin/update -updateweb Main
loads all versions of all topics in Main into mongo.
- IF MongoDB already has all versions of all topics for Main loaded, and
- IF some topics have multiple versions but none have
_latestIsLoaded
true, such that db.current.find({_topic: 'AcaciaGroup', _latestIsLoaded: NumberLong(1)})
yields zero results but db.current.find({_topic: 'AcaciaGroup', _latestIsLoaded: NumberLong(0)})
does
- THEN those topics will fail to match any SEARCH (and can harm topic-based *Group membership)
So, please let's have a sanity check so that re-importing webs with these kinds of semi-mangled topics are fixed up so that at least one of the versions has
_latistIsLoaded
true
The work-around is to run
./rest /MongoDBPlugin/update -updateweb Main -revision off
which seems to fixup
_latestIsLoaded
--
PaulHarvey - 03 May 2012