Re: DisMax handler and single-word phrase queries

2006-10-31 Thread Chris Hostetter

This is something i really went back and forth on when i was first
developing DisMax ... I initially assumed it would make sense to ignore
the pf for single word queries, but for a variety of reasons i don't
really remember in depth i decided that was a bad idea.  i think one of
the reasons was that without the pf clause contributing to the score, it
was hard to pick boost values and numeric constants in the bq and bf
params that would work for both single word and phrase queries.

what i tend to do with various indexes is some combination of:
  1) make sure the qf and pf boosts of any fields which are in both
 params take into consideration that the field is in both, and
 shouldn't be as high as a field in only one.
  2) make the pf boosts significantly greater then the qf boosts (which
 tends to make sense if you think about it)
  3) minimize the number of fields in both the qf and the pf ... in many
 cases it makes sense to have one or two amalgamated fields in the qf,
 but lots of specificfields in the pf.

As you oint out: different analyzers for differnet fields can make "I-Pod"
a term query on some fields, and a phrase queryon others -- which makes
changing the query structure problamatic.

: Date: Mon, 30 Oct 2006 17:39:00 -0800
: From: Mike Klaas <[EMAIL PROTECTED]>
: Reply-To: solr-dev@lucene.apache.org
: To: solr-dev@lucene.apache.org
: Subject: DisMax handler and single-word phrase queries
:
: Hello,
:
: If you pass a single-word querystring to dismax, it constructs a
: DisjunctionMax query with a clause for the main query, as well as a
: clause for the "phrase" boost of the single word.  This causes an
: effective doubling of the score for fields which are in both qf and
: pf.
:
: This can be corrected on the client side by conditionally unsetting pf
: for single-word queries, but I was curious if this is a situation that
: dismax might want to detect.
:
: The main difficulty from my perspective is that a single word query
: can expand to multiple terms after analysis...
:
: cheers,
: -Mike
:



-Hoss



[jira] Commented: (SOLR-58) Change Admin components to return XML like the rest of the system

2006-10-31 Thread Bill Au (JIRA)
[ 
http://issues.apache.org/jira/browse/SOLR-58?page=comments#action_12445919 ] 

Bill Au commented on SOLR-58:
-

ping.jsp does not retrun any content.  It checks the solr server by sending the 
query  defined in SolrConfig.xml (pingQuery) and returns 200 if the query works 
without any exception.  Otherwise it returns 500.

action.jsp is a secondary JSP that performs action from the main page 
(enable/disable) and the logging page (set log level).  So I agree that there 
is probably no need to XMLized it.

> Change Admin components to return XML like the rest of the system
> -
>
> Key: SOLR-58
> URL: http://issues.apache.org/jira/browse/SOLR-58
> Project: Solr
>  Issue Type: New Feature
>  Components: web gui
>Reporter: Otis Gospodnetic
> Assigned To: Otis Gospodnetic
>Priority: Minor
>
> I need to expose the admin functionality to an external application.  I think 
> returning admin data as XML may be a good and simple first step towards that.
> To do that I think I'll mostly need to modify JSPs (but I haven't had a good 
> look at Admin GUI yet).  From what I saw a few weeks ago when I briefly 
> looked at this, no Java code will need to be modified.  If you have concrete 
> ideas about how this should be done, please comment before I start next week 
> (week of October 23rd 2006).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira