[
https://issues.apache.org/jira/browse/SOLR-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199076#comment-13199076
]
Hoss Man commented on SOLR-3047:
--------------------------------
I can't make heads of tails of this bug report ... at a minimum we need to
see...
* what the full request params look like for an example request
* what the debugQuery output looks like for an example request (including the
echoParams and query parsing info
* how the requesthandler in use is configured
* the fieled and filedtype information for every field used by dismax (ie:
mentioned in the request params or request handler defaults)
> DisMaxQParserPlugin drops my field in the phrase field list (pf) if it uses
> KeywordTokenizer instead of StandardTokenizer or Whitespace
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-3047
> URL: https://issues.apache.org/jira/browse/SOLR-3047
> Project: Solr
> Issue Type: Bug
> Reporter: Antony Stubbs
>
> Has this got something to do with the minimum clause = 2 part in the code? It
> drops it without warning - IMO it should error out if the field isn't
> compatible.
> If it is on purpose - i don't see why. I split with the ngram token filter,
> so there is def more than 1 clause in the indexed field.
--
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: [email protected]
For additional commands, e-mail: [email protected]
