Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@lucene.apache.org
Message-ID: <21438023.11081287588745966.JavaMail.jira@thor>
Date: Wed, 20 Oct 2010 11:32:25 -0400 (EDT)
From: "Koji Sekiguchi (JIRA)" <jira@apache.org>
To: dev@lucene.apache.org
Subject: [jira] Commented: (SOLR-2126) highlighting multicore searches
 relying on q.alt gives NPE
In-Reply-To: <86405.309231285043253039.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Koji Sekiguchi commented on SOLR-2126:
--------------------------------------

David, I recently committed SOLR-2148. I'm not sure it fixes your problem, but can you try the latest 3x or trunk to see if it solves your problem? 

> highlighting multicore searches relying on q.alt gives NPE
> ----------------------------------------------------------
>
>                 Key: SOLR-2126
>                 URL: https://issues.apache.org/jira/browse/SOLR-2126
>             Project: Solr
>          Issue Type: Bug
>          Components: highlighter
>    Affects Versions: 1.4
>         Environment: I'm on a trunk release from early March, but I also just verified this on LucidWorks 1.4 which I have handy.
>            Reporter: David Smiley
>            Priority: Minor
>
> To reproduce this, run the example multicore solr configuration.  Then index each example document into each core.  Now we're going to do a distributed search, with q.alt=*:* and defType=dismax.  Normally, these would be set in a request handler config as defaults but we'll put them in the url to make it clear they need to be set and because the default multicore example config is so bare bones that it doesn't already have a dismax setup.  We're going to enable highlighting.
> http://localhost:8983/solr/core0/select?hl=true&q.alt=*:*&defType=dismax&shards=localhost:8983/solr/core0,localhost:8983/solr/core1
> java.lang.NullPointerException
> 	at org.apache.solr.handler.component.HighlightComponent.finishStage(HighlightComponent.java:130)
> 	at org.apache.solr.handler.component.SearchHandler.handleRequestBody(SearchHandler.java:296)
> 	at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:131)
> 	at org.apache.solr.core.SolrCore.execute(SolrCore.java:1316)
> 	at org.apache.solr.servlet.SolrDispatchFilter.execute(SolrDispatchFilter.java:338)
> 	at org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:241)
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089)
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365)
> 	at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
> 	at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
> 	at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:211)
> 	at org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
> 	at org.mortbay.jetty.Server.handle(Server.java:285)
> 	at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
> 	at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
> 	at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
> 	at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
> 	at org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
> 	at org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
> Since I happen to be using edismax in trunk, it was easy for me to work around this problem by renaming my q.alt parameter in my request handler defaults to just "q" since edismax understands raw lucene queries.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org