Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Lucene: Java-Dev

[jira] [Updated] (SOLR-2857) Multi-content-type /update handler

 

 

Lucene java-dev RSS feed   Index | Next | Previous | View Threaded


jira at apache

Apr 20, 2012, 5:13 PM

Post #1 of 6 (166 views)
Permalink
[jira] [Updated] (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 updated SOLR-2857:
--------------------------------

Attachment: SOLR-2857-update-content-type.patch

Here is a patch that moves XML,CSV,JSON,javabin and XML+XSLT into a single handler that picks the right Loader based on the content type.

The bulk of the patch is cleaning up the test config files and moving private inner classes to their own file.

The single endpoint simplifies the oddities of multiple request formats in SolrServers

This handles XSLT by looking for the 'tr' param when the content type is XML





> 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-unsubscribe [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 23, 2012, 10:06 PM

Post #2 of 6 (147 views)
Permalink
[jira] [Updated] (SOLR-2857) Multi-content-type /update handler [In reply to]

[ 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-update-content-type.patch

cleans things up a bit more, but the UpdateRequestHandler is still hardcoded for CSV,XML,JSON, and javabin

Next I will move more things around and clean up the API so it promotes registering Map<String,ContentStreamLoader>


> 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, 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 [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 23, 2012, 10:08 PM

Post #3 of 6 (149 views)
Permalink
[jira] [Updated] (SOLR-2857) Multi-content-type /update handler [In reply to]

[ 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-update-content-type.patch

last patch was missing files

> 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, 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 [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

Apr 23, 2012, 11:45 PM

Post #4 of 6 (148 views)
Permalink
[jira] [Updated] (SOLR-2857) Multi-content-type /update handler [In reply to]

[ 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 [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

May 7, 2012, 11:20 AM

Post #5 of 6 (127 views)
Permalink
[jira] [Updated] (SOLR-2857) Multi-content-type /update handler [In reply to]

[ 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

This patch is updated to trunk

I would like to commit this in the next couple days, and (possibly) look at configuration in a later issue.

> 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-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 [at] lucene
For additional commands, e-mail: dev-help [at] lucene


jira at apache

May 7, 2012, 5:25 PM

Post #6 of 6 (126 views)
Permalink
[jira] [Updated] (SOLR-2857) Multi-content-type /update handler [In reply to]

[ 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

updated with a deprecated replacement for XmlUpdateRequestHandler

> 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-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 [at] lucene
For additional commands, e-mail: dev-help [at] lucene

Lucene java-dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.