lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Høydahl (JIRA) <>
Subject [jira] [Updated] (SOLR-3439) Make SolrCell easier to use out of the box
Date Sat, 04 Aug 2012 01:01:18 GMT


Jan Høydahl updated SOLR-3439:

    Attachment: SOLR-3439.patch

Updated patch
* Adds a "url" field to schema intended for HTML/web docs. Displayed in result if found
* If "url" field is filled, it is used as href on the title link, else fallback to file:///resourcename
or to plain "id"
* Detects file type from content_type field with fallback to filename suffix

Will commit shortly
> Make SolrCell easier to use out of the box
> ------------------------------------------
>                 Key: SOLR-3439
>                 URL:
>             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, 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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message