[
https://issues.apache.org/jira/browse/SOLR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13140071#comment-13140071
]
Erik Hatcher commented on SOLR-2857:
------------------------------------
A note of caution here... content-type cannot be determined without first
getting the stream (or reader) with some recent changes on trunk (to avoid
unused content streams hitting URLs unnecessarily). So the "director" aspect
of a new catch-all /update will need to get the stream to determine the type,
then hand that stream off to a loader. This seems like it'd entail some other
refactorings to accommodate?
> 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
>
>
> 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
