lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ramirez, Paul M (388J)" <>
Subject Re: Namespaces in response (SOLR-1586)
Date Wed, 09 Dec 2009 19:36:19 GMT
Hey All,

I think Eric is right on here and what I thought the intent of the patch was. Facilitating
integration of Solr into environments where there is not "one true XML output". In addition,
there shouldn't be "one true JSON output" for cases where your existing code already has a
way it expects the JSON. Why not allow someone to write a JSON output that feeds directly
into that tool without having to change that tool. This is what makes Solr so cool is because
of its flexibility and to limit that would be a shame. None of this really has to limit the
internal representation or what the Solr community builds to support it's format but don't
unnecessarily relegate that functionality to XSLT.


On 12/9/09 11:22 AM, "Eric Pugh" <> wrote:

Is this the opportunity of having more then one XML output type?  I
mean, XML is meant to be a transport medium for data, and maybe moving
from a "one true XML output" for Solr to being able to support
multiple outputs dependent on the consumer would be useful.  I can see
it making it easier to plug Solr into environments that expect data in
certain formats, without doing an extra XSL transformation?


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message