[
https://issues.apache.org/jira/browse/SOLR-3439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13420384#comment-13420384
]
Jack Krupansky commented on SOLR-3439:
--------------------------------------
I haven't actually tried the new patch (and may not be able to until next
weekend), but looking at the patch itself, overall it looks like it is headed
in the right direction. A couple of quick comments:
1. Any reason to limit it to 5.0 and not backport to 4.0?
2. I beat my head against the wall hoping to get the file name automatically,
but if you stream a file via curl or something similar that info is not passed
along. The one hope I hold out is that maybe we should modify the post tool to
recognize that the file type is not ".xml" and then send rich documents to
SolrCell with an explicit literal to initialize the "filename" field - which
itself needs to be added.
3. Feel free to give yourself equal attribution since you have done so much
additional work.
4. It would be nice to include my sample Word and PDF documents, or other
equivalent sample rich documents to include in the exampledocs directory since
we don't have any readily accessible rich documents (a couple may be "hidden"
elsewhere.)
5. I'll volunteer to do at least some of the wiki update once the patch is
committed (or there is at least agreement to commit it.)
> Make SolrCell easier to use out of the box
> ------------------------------------------
>
> Key: SOLR-3439
> URL: https://issues.apache.org/jira/browse/SOLR-3439
> Project: Solr
> Issue Type: Improvement
> Components: contrib - Solr Cell (Tika extraction), Schema and
> Analysis
> Reporter: Jack Krupansky
> Assignee: Jan Høydahl
> Priority: Minor
> Fix For: 4.0, 5.0
>
> Attachments: Lincoln-Gettysburg-Address.docx,
> Lincoln-Gettysburg-Address.pdf, SOLR-3439.patch, SOLR-3439.patch,
> SOLR-3439.patch
>
>
> Currently, SolrCell is configured to map Tika "content" (the main body of a
> document) to the "text" field which is the indexed-only (not stored)
> catch-all for default queries. That searches fine, but doesn't show the
> document content in the results, sometimes leading users to think that
> something is wrong. Sure, the user can easily add the field (and this is
> documented), but it would be a better user experience to have such a basic
> feature work right out of the box without any config editing and without the
> need for the user to read the fine print in the documentation.
> I propose that we add the "content" field to the example schema in the
> section of fields already defined to support SolrCell metadata.
--
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]
