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

Munendra S N commented on SOLR-4382:
------------------------------------

[~iorixxx]
In SOLR-5163, support for the check on unknown fields in *qf* has been added. 
So, when an unknown field is specified then, the request fails with Exception 
*Undefined field in qf*.
In case, you don't want the request to fail then *<dynamicField name="*" 
type="ignored" />* can be added to the schema (the solution suggested by you)

> edismax, qf, multiterm analyzer, wildcard query bug
> ---------------------------------------------------
>
>                 Key: SOLR-4382
>                 URL: https://issues.apache.org/jira/browse/SOLR-4382
>             Project: Solr
>          Issue Type: Bug
>          Components: query parsers, Schema and Analysis, search
>    Affects Versions: 4.0, 4.1
>            Reporter: Ahmet Arslan
>            Priority: Major
>         Attachments: SOLR-4382.patch
>
>
> If I fire a wildcard query o*t*v*h using edismax, and add a non existed field 
> to qf parameter, i get this phrase query at the end. (with 
> autoGeneratePhraseQueries="true")
> http://localhost:8983/solr/collection1/select?q=O*t*v*h&wt=xml&debugQuery=on&defType=edismax&qf=sku%20doesNotExit
> parsedquery = (+DisjunctionMaxQuery((sku:"o t v h")))/no_coord
> parsedquery_toString = +(sku:"o t v h")
> Existing field(s) works as expected :
> http://localhost:8983/solr/collection1/select?q=O*t*v*h&wt=xml&debugQuery=on&defType=edismax&qf=sku
> yields
> (+DisjunctionMaxQuery((sku:o*t*v*h)))/no_coord
> +(sku:o*t*v*h)
> For a workaround I enabled following dynamic field :
> <dynamicField name="*" type="ignored" />
> User list link : http://search-lucene.com/m/zB104LKTRI



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to