[ https://issues.apache.org/jira/browse/SOLR-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan McKinley updated SOLR-2857:
--------------------------------
Attachment: SOLR-2857-content-type-refactor.patch
Here is another version that refactors the base classes to better support reuse and a registry
{code:java}
loaders.put("application/xml", new XMLLoader().init(p) );
loaders.put("application/javabin", new JavabinLoader().init(p) );
loaders.put("application/json", new JsonLoader().init(p) );
loaders.put("text/csv", new CSVLoader().init(p) );
{code}
Are people worried about back-compatibility of the ContentStreamLoader classes? Ignoring
3.x API will make the final solution much cleaner
> 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-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
|