You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ryan McKinley (JIRA)" <ji...@apache.org> on 2012/05/08 23:39:50 UTC
[jira] [Resolved] (SOLR-2857) Multi-content-type /update handler
[ https://issues.apache.org/jira/browse/SOLR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryan McKinley resolved SOLR-2857.
---------------------------------
Resolution: Fixed
Assignee: Ryan McKinley
I added this in #1335768, and have put rough docs on the wiki -- I'm sure there are more links/references that should be updated
> 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
> Assignee: Ryan McKinley
> Fix For: 4.0
>
> Attachments: SOLR-2857-content-type-refactor.patch, SOLR-2857-content-type-refactor.patch, SOLR-2857-content-type-refactor.patch, SOLR-2857-update-content-type.patch, SOLR-2857-update-content-type.patch, 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org