[ 
https://issues.apache.org/jira/browse/SOLR-3246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13229747#comment-13229747
 ] 

Jan Høydahl commented on SOLR-3246:
-----------------------------------

We wrote a data dumper in a project as a patched 
ExtractingUpdateRequestHandler. It writes a CSV format (including Base64 
encoded binary input) to one file. We were thinking about rewriting it as an 
UpdateProcessor, which will then work much like yours. The benefit with CSV 
format is that it is much more compact. Also, a file system may kneal with too 
many files in a folder.
                
> UpdateRequestProcessor to extract Solr XML from rich documents
> --------------------------------------------------------------
>
>                 Key: SOLR-3246
>                 URL: https://issues.apache.org/jira/browse/SOLR-3246
>             Project: Solr
>          Issue Type: New Feature
>          Components: update
>            Reporter: Emmanuel Espina
>            Priority: Minor
>         Attachments: SOLR-3246.patch
>
>
> This would be an update request handler to save a file with the xml that 
> represents the document in an external directory. The original
> idea behind this was to add it to the processing chain of the 
> ExtractingRequestHandler to store an already parsed version of the docs. This 
> storage of pre-parsed documents will make the re indexing of the entire index 
> faster (avoiding the Tika phase, and just sending the xml to the standard 
> update processor).
> As a side effect, extracting the xml can make debugging of rich docs easier.

--
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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to