[ https://issues.apache.org/jira/browse/SOLR-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199125#comment-13199125 ]
Antony Stubbs commented on SOLR-3047: ------------------------------------- It just seems that if the field tokeniser only produces a single token (as keywordtokenizer produces), it gets silently dropped from phrase list queries (even though multiple tokens are produced by the ngramfilter in the end). If I just change the tokenizer to standard, it works as expected. > 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org