[
https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595372#action_12595372
]
Chris Harris commented on SOLR-284:
-----------------------------------
I'm on the fence about whether this patch makes sense to include in Solr right
now. One thing I'm wondering, though: Can we assess the odds at this point
whether it could make sense for a Tika-based handler to offer the same public
interface that the handler in this patch presents? That is, even if the
underlying implementation were switched to Tika at some point, could we avoid
changing the URL schema and such that Solr clients would use to interact with
it?
If it's likely that the public interface could indeed remain the same for the
first Tika-based handler release (or at least more or less the same), would
this alleviate any of Grant's concerns?
Also, would putting this handler into a contrib directory rather than in the
main code base, as has been mentioned on the mailing list, make committing it
any less problematic?
> Parsing Rich Document Types
> ---------------------------
>
> Key: SOLR-284
> URL: https://issues.apache.org/jira/browse/SOLR-284
> Project: Solr
> Issue Type: New Feature
> Components: update
> Affects Versions: 1.3
> Reporter: Eric Pugh
> Fix For: 1.3
>
> Attachments: libs.zip, rich.patch, rich.patch, rich.patch,
> rich.patch, source.zip, test-files.zip, test-files.zip, test.zip
>
>
> I have developed a RichDocumentRequestHandler based on the CSVRequestHandler
> that supports streaming a PDF, Word, Powerpoint, Excel, or PDF document into
> Solr.
> There is a wiki page with information here:
> http://wiki.apache.org/solr/UpdateRichDocuments
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
