Are you wanting to do thin on every single user query, and present to the end user which words matched where? In that case debugQuery may be too much, and I would look into creating a custom debugComponent optimized to only outputting the core parts of the "explain" section that you need.
If this is some support department admin tool, I would recommend implementing a hidden query parameter in your front-end, which turns on debugQuery=true and pulls out the "explain" part, parses it and outputs a simple list of matching terms in each field inline - for admin users only. What info are you missing from debugQuery? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com Training in Europe - www.solrtraining.com On 18. juni 2010, at 12.02, Lukas Kahwe Smith wrote: > > On 18.06.2010, at 12:00, Fornoville, Tom wrote: > >> Hi Lukas, >> >> Have you tried setting the debug mode (debugQuery=on)? >> It provides very detailed info about the scoring, it might even be too >> much for a regular user but for us it was very helpful at times. > > > yeah .. that was the second thing i looked at. it doesnt really contain the > infos required, plus its obviously quite slow too. > > regards, > Lukas Kahwe Smith > m...@pooteeweet.org > > >
