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

David Smiley commented on SOLR-3269:
------------------------------------

I'm a little confused at what the problem is.  If you simply omit 
<defaultSearchField> (comment it out) are things okay?  FYI in SOLR-2724 I got 
some consensus to deprecate/remove defaultSearchField and the default query 
operator from schema.xml -- you use use q.df and q.op.  I just haven't gotten 
around to it.
                
>  <defaultSearchField>name</defaultSearchField> should not reject 
> non-indexable query fields
> -------------------------------------------------------------------------------------------
>
>                 Key: SOLR-3269
>                 URL: https://issues.apache.org/jira/browse/SOLR-3269
>             Project: Solr
>          Issue Type: Bug
>          Components: Schema and Analysis
>    Affects Versions: 3.5
>            Reporter: Benson Margulies
>            Priority: Minor
>
> I have a custom query processing component that maps field names. So, I want 
> the default field to be a field that is indexed='false', because a lucene 
> index on it is useless. The RequestHandler I have takes that field from the 
> query and maps it to booleans on other fields.
> It would be nice if the schema check did not reject my attempt to list this 
> field as the default search field when it is not indexed.

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

Reply via email to