[
https://issues.apache.org/jira/browse/SOLR-5163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621998#comment-16621998
]
David Smiley commented on SOLR-5163:
------------------------------------
Aliases can refer to other aliases and it's resolved recursively. Based on the
patch here, if an alias refers to a bogus field, then the new checks wouldn't
catch it. It's not a blocker to mean but it is a shortcoming. You might also
want to see if the field is an alias first to avoid the throw of an exception
that may be innocent. FYI ExtendedSolrQueryParser validateCyclicAliasing does
some checks vaguely similar to what might be needed.
> 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: [email protected]
For additional commands, e-mail: [email protected]
