QueryElevationComponent results only show up with debug = true
Hi, I'm using solr 4.0 final built around Dec 2012. I was initially told that the QEC didn't work for distributed search but apparently it was fixed. Anyway, I use the /elevate handler with [elevated] in the field list and I don't get any elevated results. elevated=false in the result block. however, if I turn on debugQuery; the elevated result appears in the debug section under queryBoost. Is this the only way you can get elevated results? Because before (and I can't remember if this was before or after I went to 4.0 Final) I would get the elevated results mixed in with the regular results in the result block. elevated=true was the only way to tell them apart. I also tried forceElevation, enableElevation, exclusive but there is still no elevated results in the result block. What am I doing wrong? query: http://localhost:8080/solr/Profiles/elevate?q=gangnam+stylefl=*,[elevated]wt=xmlstart=0rows=100enableElevation=trueforceElevation=truedf=textqt=edismaxdebugQuery=true Here's my config: searchComponent name=elevator class=solr.QueryElevationComponent str name=queryFieldTypetext_general/str str name=config-fileelevate.xml/str /searchComponent requestHandler name=/elevate class=solr.SearchHandler startup=lazy lst name=defaults str name=echoParamsexplicit/str str name=dftext/str /lst arr name=last-components strelevator/str /arr /requestHandler elevate.xml elevate query text=gangnam style doc id=https://server/profiles/html/profileView.do?key=ec6de388-fb7a-4397-9ed5-51760e4333d3; / /query /elevate -- View this message in context: http://lucene.472066.n3.nabble.com/QueryElevationComponent-results-only-show-up-with-debug-true-tp4087531.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: QueryElevationComponent results only show up with debug = true
: What am I doing wrong? : query: : http://localhost:8080/solr/Profiles/elevate?q=gangnam+stylefl=*,[elevated]wt=xmlstart=0rows=100enableElevation=trueforceElevation=truedf=textqt=edismaxdebugQuery=true You've shown up the configs you are using, and the query you executed, and you've said that you see evidence of the QueryElevationComponent working according to the debug score explanation -- but you haven't shown us the actaul response of your sample query so we can understand what exactly you are getting in response. w/o that it's hard to understand what you are seeing and make any guesses as to what might be going wrong. Can you please show us the response of that example query -- and if that example response doesn't include the doc from your elevate.xml, can you change the exampl (increase rows or whatever) so that it does so we can see evidence that it's really in your index and not getting elevated? : Here's my config: : searchComponent name=elevator class=solr.QueryElevationComponent : : str name=queryFieldTypetext_general/str : str name=config-fileelevate.xml/str : /searchComponent : : : requestHandler name=/elevate class=solr.SearchHandler startup=lazy : lst name=defaults : str name=echoParamsexplicit/str : str name=dftext/str : /lst : arr name=last-components : strelevator/str : /arr : /requestHandler : elevate.xml : elevate : query text=gangnam style : doc : id=https://server/profiles/html/profileView.do?key=ec6de388-fb7a-4397-9ed5-51760e4333d3; : / : /query : : /elevate : : : : : -- : View this message in context: http://lucene.472066.n3.nabble.com/QueryElevationComponent-results-only-show-up-with-debug-true-tp4087531.html : Sent from the Solr - User mailing list archive at Nabble.com. : -Hoss
Re: QueryElevationComponent results only show up with debug = true
Sure, Here are the results with the debugQuery=true; with debugging off, there are no results. The elevated result appears in the queryBoost section but not in the result section: ?xml version=1.0 encoding=utf-8? response lst name=responseHeader int name=status0/int int name=QTime0/int lst name=params str name=enableElevationtrue/str str name=wtxml/str str name=rows100/str str name=fl*,[elevated]/str str name=dftext/str str name=debugQuerytrue/str str name=start0/str str name=qgangnam/str str name=forceElevationtrue/str str name=qtedismax/str /lst /lst result name=response numFound=0 start=0/result lst name=debug lst name=queryBoosting str name=qgangnam/str arr name=match str https://server/profiles/html/profileView.do?key=ec6de388-fb7a-4397-9ed5-51760e4333d3/str /arr /lst str name=rawquerystringgangnam/str str name=querystringgangnam/str str name=parsedquery(text:gangnam ((id:https://server/profiles/html/profileView.do?key=ec6de388-fb7a-4397-9ed5-51760e4333d3)^0.0))/no_coord/str str name=parsedquery_toStringtext:gangnam ((id:https://server/profiles/html/profileView.do?key=ec6de388-fb7a-4397-9ed5-51760e4333d3)^0.0)/str lst name=explain / str name=QParserLuceneQParser/str lst name=timing double name=time0.0/double lst name=prepare double name=time0.0/double lst name=org.apache.solr.handler.component.QueryComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.FacetComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.MoreLikeThisComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.HighlightComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.StatsComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.QueryElevationComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.DebugComponent double name=time0.0/double /lst /lst lst name=process double name=time0.0/double lst name=org.apache.solr.handler.component.QueryComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.FacetComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.MoreLikeThisComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.HighlightComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.StatsComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.QueryElevationComponent double name=time0.0/double /lst lst name=org.apache.solr.handler.component.DebugComponent double name=time0.0/double /lst /lst /lst /lst /response -- View this message in context: http://lucene.472066.n3.nabble.com/QueryElevationComponent-results-only-show-up-with-debug-true-tp4087531p4087554.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: QueryElevationComponent results only show up with debug = true
I can guarantee you that the ID is unique and it exists in that index. -- View this message in context: http://lucene.472066.n3.nabble.com/QueryElevationComponent-results-only-show-up-with-debug-true-tp4087531p4087565.html Sent from the Solr - User mailing list archive at Nabble.com.
Re: QueryElevationComponent results only show up with debug = true
: Here are the results with the debugQuery=true; with debugging off, there are : no results. I don't understand what you mean. According to this response, with debugQuery=true, there are not results matching your query... : result name=response numFound=0 start=0/result : The elevated result appears in the queryBoost section but not in the : result section: Again: i odn't understand what you mean -- the debug output is just showing you that your QEC is in fact configured to boost a particular document for this query, and it's telling you the ID it's trying to boost based on your config -- that doesn't mean the *result* is in the queryBoost section. As far as i can tell from this, the document you wnat to boost either isn't in your index at all, or doesn't match your query. please see my previous comment... Can you please show us the response of that example query -- and if that example response doesn't include the doc from your elevate.xml, can you change the exampl (increase rows or whatever) so that it does so we can see evidence that it's really in your index and not getting elevated? ...can you show us *any* query that proves a document with that ID exists in the index? Ignoring QEC for a moment, can you use debugQuery=true and explainOther to see if/why that document doesn't seem to match your query at all? -Hoss
