[
https://issues.apache.org/jira/browse/SOLR-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621903#comment-16621903
]
Charles Sanders commented on SOLR-5163:
---------------------------------------
[~eribeiro] Initially I put the check in DismaxQueryParser#parseQueryFields,
as seen in the first patch. But existing unit tests for field aliases failed.
The method DismaxQueryParser#parseQueryFields does not know about field
aliases. That is why I moved the check to ExtendedDismaxQParser.
As for the unit test, I attempted to follow the pattern established in
TestExtendedDismaxParser. There are many tests in the class that use the same
string comparison pattern. ???
This is a very large repository of code. Still trying to get a foot hold. I
would be very interested to see and learn from a patch you create for this
issue.
> edismax should throw exception when qf refers to nonexistent field
> ------------------------------------------------------------------
>
> Key: SOLR-5163
> URL: https://issues.apache.org/jira/browse/SOLR-5163
> Project: Solr
> Issue Type: Bug
> Components: query parsers, search
> Affects Versions: 4.10.4
> Reporter: Steven Bower
> Assignee: David Smiley
> Priority: Major
> Labels: newdev
> Attachments: SOLR-5163.patch, SOLR-5163.patch
>
>
> query:
> q=foo AND bar
> qf=field1
> qf=field2
> defType=edismax
> Where field1 exists and field2 doesn't..
> will treat the AND as a term vs and operator
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
