I have updated iyp_geoexpansions synonym dictinary at the fastf-rigg with the new geodata from thomas. After the update all results are prefixed with "1###" So a query for "torshov" which would return SUGGESTED NEW QUERY "oslo" before the dic. update will now return SUGGESTED NEW QUERY "1###oslo" This is because you can have several synonyms related, and you can give them weights.
If you really really dislike the prefix I can look for ways to avoid it, but I'd rather spend time on other issues right now. I believe a much quicker and easy solution is to have martin trim off the prefix in java in this particular geoexpansion query. On Thu, 2008-06-05 at 17:28 +0200, Mick Semb Wever wrote: > On Thu, 2008-06-05 at 16:49 +0200, Jon Martin Solaas wrote: > > So the suggested query that appeared as "oslo" > > yesterday now appears as "1###oslo" today. Which is a little closer to > > the format AbstractSimpleFastSearchCommand.collectRelevantQueries would > > accept initially (e.g. contains some #-chars ...), but the value is > > interpreted as "1" and not "oslo". > > Could you better explain what has changed in the fast index to have > caused this change, as it breaks _all_ relevantQueries! > Hep, Glenn-erik, or MortenT can help you out maybe. > > ~mck > _______________________________________________ Kernel-development mailing list [email protected] http://sesat.no/mailman/listinfo/kernel-development
