So, summing up all the information i now have, and the fact I have some additional custom components that use fieldcache, such that the specific answer for field collapsing by migrating to solr 4.0 is not a complete solution to my problems,
it seems to me more and more like I might have to actually implement a custom solr QueryComponent, whereby I will pass it multiple collectors (perhaps via some kind of MultiCollector interface, similar to Grouping uses) which will do their appropriate field value collection/aggregation as results are being fetched. In other words, using a per-segment fieldcache collection as a post-processing step (e.g after QueryComponent did its collection) does not seem at all trivial, if at all possible ( is it possible? ) Is this accurate? Thanks again for all the info here.. Adam On Mon, Dec 6, 2010 at 1:48 PM, Ryan McKinley <ryan...@gmail.com> wrote: > On Mon, Dec 6, 2010 at 4:02 PM, Yonik Seeley <yo...@lucidimagination.com> > wrote: > > On Mon, Dec 6, 2010 at 3:41 PM, Adam H. <jimmoe...@gmail.com> wrote: > >> Fair enough - I might give it a shot if most functionality is compatible > to > >> solr 1.4.1 to your mind? and is fairly stable? > > > > Yes, the external APIs are very compatible. > > The internal APIs - not so much. > > You should reindex also. > > And not be (too) surprised if things change before the official 4.x > release -- the chances are good that something will change that may > require reindexing. > > ryan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org > >
