Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Mon, 7 May 2012 02:20:50 +0000 (UTC)
From: "Jack Krupansky (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <2073546893.32757.1336357250174.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1986839461.30859.1336251228735.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (SOLR-3439) Add "content" field to example
 schema to make SolrCell easier to use out of the box
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jack Krupansky commented on SOLR-3439:
--------------------------------------

The concept of copyField is implicitly a judgment that a query of the merged fields is significantly better than the dismax query of the separate fields. But, is that really the case?

And it is common to boost various document components differently, such as the title.

That said, I am a little reluctant to change the overall pattern/approach simply to add one field. Maybe the pattern change should be a separate issue.

                
> Add "content" field to example schema to 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
>            Priority: Minor
>             Fix For: 4.0
>
>         Attachments: Lincoln-Gettysburg-Address.docx, Lincoln-Gettysburg-Address.pdf, 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. It would be stored and indexed.
> I further propose that a copyField be added for the "title", "description", (and maybe a couple of others) and "content" fields to add them to the "text" field for searching. Again, trying to improve the out of the box user experience. It also simplifies testing - less setup.

--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org