lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antony Stubbs (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-3047) DisMaxQParserPlugin drops my field in the phrase field list (pf) if it uses KeywordTokenizer instead of StandardTokenizer or Whitespace
Date Thu, 02 Feb 2012 19:12:53 GMT

    [ https://issues.apache.org/jira/browse/SOLR-3047?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13199111#comment-13199111
] 

Antony Stubbs commented on SOLR-3047:
-------------------------------------

Ok, I'll try to reproduce it in a simple setup.
                
> 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


Mime
View raw message