[
https://issues.apache.org/jira/browse/SOLR-2126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12923623#action_12923623
]
David Smiley commented on SOLR-2126:
------------------------------------
Following the instructions in my description here, I see that the bug is no
longer present. Thanks Koji.
BTW, there seems to be a problem with the multicore example config in trunk; it
fails to start up properly due to a lack of index segments. Weird. I copied
some out of another index.
> 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: [email protected]
For additional commands, e-mail: [email protected]
