Reply to comment

In the stitches demo, there is the need to search for objects in stitches by ContentDef, Content and Content Version.  These searches are "admin" oriented, in that, only an admin tool would utilize these searches.  The main search that powers stitches is compass-powered.  The question was whether to use compass for these 3 searches.
I added the objects (ContentDf, Content, ContentVersion) to the compass index, but not really happy with it.  The contentversion is a pretty bloated Lucene Document and the admin search doesn't need all this information, which of course, the main stitches searche does need all this info.
I am thinking of using the database powered search (findNameByILike) for this function.  It would keep the performance of the indexing fast (since we would effectively cut the total index size by 50%).