Hi Richard Your "solution" has been discussed on the list before too. But IIRC people more familiar with Lucene than me advised us not to go this way because the "score" you get is only valid for the repository/index you got it from and is not comparable with other scores you might have for other hits from other repositories/indexes.
See http://www.mail-archive.com/[email protected]/msg03917.html I think some more "magic" has to be applied in order for the results to be merged, don't you? -will On 29.10.2010, at 14:52, Unger, Richard wrote: > > Hi Everyone! > > We have just solved this problem as follows: > > 1. Wrote our own model-class to handle the search, subclassed > SearchResultItem. > 2. Perform 2 searches, once for each repository. > 3. Combine the results, sort by score. > 4. Display combined results. > > If using community edition, this approach will work with no problems, > although some care must be taken on how the results are combined if you have > a large amount of content and want acceptable performance. > > If using enterprise edition, you will have to invest some thought on how to > handle the DMS searches in a multi-site environment. For the website repo the > solution is obvious: search only within the subtree belonging to your site. > For the DMS repo, it depends how you have organized it (whether the different > sites share the same DMS) whether it makes sense to search the whole repo, a > subpath, or just certain nodes. > > Using SQL- rather than XPATH-queries can help keep the size of the result > lists down, since you can limit the size of the result-set when using the SQL > syntax. > > Regards from Vienna, > > Richard > > > > -----Ursprüngliche Nachricht----- > Von: [email protected] > [mailto:[email protected]] Im Auftrag von Will Scheidegger > Gesendet: Freitag, 29. Oktober 2010 12:12 > An: Magnolia User-List > Betreff: [magnolia-user] Magnolia search on multiple repositories possible > after all? > > > Dear Magnolians > > This has been discussed before: How can we search the website AND dms > repository at once. Well, querying both repositories of course is easy, but > so far it was said that one cannot combine the search results sorted by > rating because each index generates its own rating in a way that they could > not be compared. > > Now I just read on the lucene website the following interesting info: > > "multiple-index searching with merged results" > > (See http://lucene.apache.org/java/docs/features.html) > > So, how of you is familiar enough with Lucene so that you could tell us how > hard it would be to use that feature in Magnolia? > > Thanks! > -will > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > > > > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- > ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
