[
https://issues.apache.org/jira/browse/SOLR-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755058#action_12755058
]
Grant Ingersoll commented on SOLR-284:
--------------------------------------
bq. How does a copyField necessitate storing the fields?
Yonik suggested his approach helps with stored values for the metadata.
bq. And how is the copyField slower than this feature mapping to a common
attribute which ends up with an equivalent outcome?
As I understand Yonik's response, he was suggesting that I use the uprefix
combined with copy fields. That involves two field entries, when I only care
about the one catch all. copyFields do have a cost, especially when you don't
need them.
At any rate, with the patch I put up, you have the option of doing it either
way.
> Parsing Rich Document Types
> ---------------------------
>
> Key: SOLR-284
> URL: https://issues.apache.org/jira/browse/SOLR-284
> Project: Solr
> Issue Type: New Feature
> Components: update
> Reporter: Eric Pugh
> Assignee: Grant Ingersoll
> Fix For: 1.4
>
> Attachments: libs.zip, rich.patch, rich.patch, rich.patch,
> rich.patch, rich.patch, rich.patch, rich.patch, schema_update.patch,
> SOLR-284-no-key-gen.patch, SOLR-284.patch, SOLR-284.patch, SOLR-284.patch,
> SOLR-284.patch, SOLR-284.patch, SOLR-284.patch, SOLR-284.patch,
> SOLR-284.patch, SOLR-284.patch, solr-word.pdf, source.zip, test-files.zip,
> test-files.zip, test.zip, un-hardcode-id.diff
>
>
> 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.
