[ http://issues.apache.org/jira/browse/SOLR-16?page=comments#action_12413033 ]
Mike Baranczak commented on SOLR-16: ------------------------------------ OK, I tried writing a test case like Hoss suggested and it kept failing when I tried to select a custom writer. I eventually figured out that this is because TestHarness is hard-coded to use XMLResponseWriter. Which made perfect sense with the old set-up, but now... I could patch TestHarness so that it honors the queryResponseWriter settings, but this wouldn't make a very useful test, since it would completely bypass the code that actually does the work of selecting the writer (in SolrServlet). And if we actually wanted to test SolrServlet, we'd have to completely rewrite the test framework. Any thoughts? > patch to allow the use of a custom query output writer > ------------------------------------------------------ > > Key: SOLR-16 > URL: http://issues.apache.org/jira/browse/SOLR-16 > Project: Solr > Type: New Feature > Components: search > Reporter: Mike Baranczak > Attachments: custom_writer.patch, custom_writer_rev2.patch > > This patch allows users to create their own implementation of > QueryResponseWriter, and specify that class in solrconfig.xml. The default > behavior is to use XMLResponseWriter like before. The class selection code > only runs once at servlet init time, so it shouldn't have any measurable > effect on performance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
