A tool for analyzing search components
Now Solr has a great tool for analysis of text processing by different fields and types (you can see what every filter gets and outputs). It would be great to have a similar tool, which would show, what information every search component receives and outpus to the next search component. Though, maybe not so many people use search components, dependent on other search components...
Artem Lukanin commented
In case of the spellcheck component, the results can be fed to the query component if collate=true. I would like to see, what suggestions were fed to change collation options without debugging. But the spellcheck component invokes the query component internally, so you have not to place "query" after "spellcheck". The debug component you propose will not help in this exact case, I think.
I can make a component, that filters or reformats the output of the previous component. So I would like to see the response at each stage to see, what the component changed in the output.
This could probably work by writing a Debug Component and sticking it in the custom chain before/after each normal component.
But what would you specifically debug? Query? Documents and Documents order? Anything else?
Dmitry Kan commented
perhaps it would be great to have some debug sort of "information flow" between components and at what stage what exactly happened?
It would help debugging issues and, possibly, coming up with better ideas of search in general.