[ http://issues.apache.org/jira/browse/SOLR-59?page=all ]
Bertrand Delacretaz updated SOLR-59:
------------------------------------
Attachment: SOLR-59-20061103.patch
> ...I think it might make more sense to use the normal query parameter
> mechanism to control this (requestHandler defaults in solrconfig). ..
I agree, but I'm not sure how to access these values, are they provided
somewhere in SolrCore, or how should I best get them?
> ...Also, why the extra addInfo element in the responseHeader?..
Right, makes no sense. This modifed patch goes back to the previous format
(still needs the additional files of attachment 3).
<responseHeader>
<status>0</status>
<QTime>1</QTime>
<lst name="explicitQueryParameters">
<str name="rows">10</str>
...
> ...should we make responseHeader consistent with the generic response format?
I think so. I didn't want to change that as it changes the existing format, but
it makes sense.
> Copy request parameters to Solr's response
> ------------------------------------------
>
> Key: SOLR-59
> URL: http://issues.apache.org/jira/browse/SOLR-59
> Project: Solr
> Issue Type: Improvement
> Reporter: Bertrand Delacretaz
> Attachments: SOLR-59-20061024.patch, SOLR-59-20061102.patch,
> SOLR-59-20061103.patch, SOLR-59-new-files-20061102.tar.gz
>
>
> This patch copies the request parameters (explicit ones only, not the
> defaults) to Solr's XML output.
> It is not configurable yet, it is enabled by default and adds a
> "queryParameters" list to the responseHeader:
> <responseHeader>
> <status>0</status>
> <QTime>1</QTime>
> <lst name="queryParameters">
> <arr name="multi">
> <str>red</str>
> <str>blue</str>
> </arr>
> <str name="rows">10</str>
> <str name="start">0</str>
> <str name="indent">on</str>
> <str name="q">solr</str>
> <str name="stylesheet"/>
> <str name="version">2.1</str>
> </lst>
> </responseHeader>
> The above example includes a multi-valued parameter, "multi".
> This might still change a bit, but if someone wants to play with it or
> improve it, here you go.
--
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
