You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Antony Stubbs (Updated) (JIRA)" <ji...@apache.org> on 2012/01/18 20:34:39 UTC
[jira] [Updated] (SOLR-3047) DisMaxQParserPlugin drops my field in
the phrase field list (pf) if it uses KeywordTokenizer instead of
StandardTokenizer or Whitespace
[ https://issues.apache.org/jira/browse/SOLR-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antony Stubbs updated SOLR-3047:
--------------------------------
Summary: DisMaxQParserPlugin drops my field in the phrase field list (pf) if it uses KeywordTokenizer instead of StandardTokenizer or Whitespace (was: DisMaxQParserPlugin drops my field in the pf option if it uses KeywordTokenizer instead of StandardTokenizer or Whitespace)
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org