lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-2857) Multi-content-type /update handler
Date Mon, 31 Oct 2011 22:19:32 GMT


Hoss Man commented on SOLR-2857:

Regardless of the implementation...
    * How to distinguish between XML and XSLT updates? Both are 'text/xml'?
    * When would the ExtractingRequestHandler be selected? On all unknown types? What if you
want to index an XML as verbatim text, but it has the XML content type?
    * There should perhaps be a parameter to let you override the auto-detection?

..these seem like the kinds of situations where you would make an explicit request to an explicitly
named handler, instead of relying on content-type detection (ie: if we remap "/update" to
some new snazzier handler, and someone says "but i want to do an xslt based update, not an
xml update" then they can POST to "/update/xslt" instead.  etc....)
> Multi-content-type /update handler
> ----------------------------------
>                 Key: SOLR-2857
>                 URL:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message