[
https://issues.apache.org/jira/browse/SOLR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258686#comment-13258686
]
Ryan McKinley commented on SOLR-2857:
-------------------------------------
What are thoughts on deprecation? I think we should go ahead and drop the
specific flavors.
Now that I think about the override parameter (and deprecation) I think it may
make sense to have something like:
{code:xml}
<requestHandler name="/update/json" class="solr.UpdateRequestHandler">
<str name="force.contentType">application/json</str>
</requestHandler>
{code}
This would make it behave like the 3.x JsonUpdateRequestHandler
> Multi-content-type /update handler
> ----------------------------------
>
> Key: SOLR-2857
> URL: https://issues.apache.org/jira/browse/SOLR-2857
> Project: Solr
> Issue Type: Improvement
> Reporter: Erik Hatcher
> Fix For: 4.0
>
> Attachments: SOLR-2857-update-content-type.patch
>
>
> Something I've been thinking about lately... it'd be great to get rid of all
> the specific update handlers like /update/csv, /update/extract, and
> /update/json and collapse them all into a single /update that underneath uses
> the content-type(s) to hand off to specific content handlers. This would
> make it much easier to toss content at Solr and provide a single entry point
> for updates.
--
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
