[
https://issues.apache.org/jira/browse/SOLR-3387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258387#comment-13258387
]
Ryan McKinley commented on SOLR-3387:
-------------------------------------
yes -- i'm looking at something like:
{code:java}
private void setDefaultWT(String wt, SolrQueryRequest req) {
SolrParams params = req.getParams();
if( params.get(CommonParams.WT) == null ) {
Map<String,String> map = new HashMap<String,String>(1);
map.put(CommonParams.WT, wt);
req.setParams(SolrParams.wrapDefaults(params,
new MapSolrParams(map)));
}
}
{code}
The big change would be that content-type is important. So far only the
charset is used. I think this is an OK change for 4.x and is inline with any
REST service
> UpdateRequestHandler should support XML,CSV,JSON, and javabin
> -------------------------------------------------------------
>
> Key: SOLR-3387
> URL: https://issues.apache.org/jira/browse/SOLR-3387
> Project: Solr
> Issue Type: Improvement
> Reporter: Ryan McKinley
> Fix For: 4.0
>
>
> Rather then have 4 handlers to support 4 content types, we should use a
> single endpoint and pick the ContentStreamLoader based on the ContentType
> This will simplify configuration problems for clients that want to swtich
> format (see SOLR-3038)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
