[
https://issues.apache.org/jira/browse/SOLR-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated SOLR-628:
--------------------------
Component/s: search
Affects Version/s: (was: 1.3)
Fix Version/s: (was: 1.3)
1.4
Summary: make forceElevation a run time option in
QueryElevationComponent (was: forceElevation=true doesn't work in
QueryElevationComponent)
tweaking issue details to reflect realty (not a bug, no affects on 1.3)
> make forceElevation a run time option in QueryElevationComponent
> ----------------------------------------------------------------
>
> Key: SOLR-628
> URL: https://issues.apache.org/jira/browse/SOLR-628
> Project: Solr
> Issue Type: Improvement
> Components: search
> Reporter: Hoss Man
> Assignee: Ryan McKinley
> Fix For: 1.4
>
> Attachments: allow.runtime.forceelevation.patch
>
>
> didn't get any reply to this in email, filing as bug to make sure it's dealt
> with before 1.3 release (either by fixing documentation, or by fixing bug --
> still not sure what the problem is)
> {quote}
> Date: Fri, 13 Jun 2008 11:41:26 -0700 (PDT)
> From: Chris Hostetter
> To: solr-user
> Subject: QueryElevationComponent and forceElevation=true ?
> I don't know much about QueryElevationComponent but perusing the wiki docs
> and trying
> it out with teh example configs i noticed that this URL didn't produce the
> output i
> expected...
> http://localhost:8983/solr/elevate?q=ipod&fl=id,price&sort=price+asc&forceElevation=true&enableElevation=true&debugQuery=true
> ..as far as i can tell, the forceElevation=true should cause "MA147LL/A" to
> always
> apear at the top, regardless of the sort -- but that doesn't seem to be the
> case.
> Am I reading the docs wrong, or is this a bug?
> {quote}
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
