Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Date: Fri, 3 Feb 2012 22:58:54 +0000 (UTC)
From: "Hoss Man (Commented) (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Message-ID: 
 <1632982167.9654.1328309934036.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2145094233.53650.1326915041620.JavaMail.tomcat@hel.zones.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
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Hoss Man commented on SOLR-3047:
--------------------------------

bq. Hoss, is there a way I can send you the example privately?

[I'd rather not|https://people.apache.org/~hossman/#private_q]

if you can't share the configs you are using, can't you at least add a quick example of something demonstrating your problem to the example schemx.xml and post that?

I just tried this example from Solr 3.5.0 (alphaNameSort uses KeywordTokenizer) and got exactly what i expected...

{code}
http://localhost:8983/solr/select?debugQuery=true&defType=dismax&qf=name&pf=alphaNameSort&q=foo%20bar%20baz

+((DisjunctionMaxQuery((name:foo)) 
   DisjunctionMaxQuery((name:bar)) 
   DisjunctionMaxQuery((name:baz))
  )~3
 ) 
 DisjunctionMaxQuery((alphaNameSort:foobarbaz))
{code}
                
> 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