lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] Commented: (SOLR-2126) highlighting multicore searches relying on q.alt gives NPE
Date Thu, 21 Oct 2010 20:44:15 GMT


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:
>             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(
> 	at org.apache.solr.handler.component.SearchHandler.handleRequestBody(
> 	at org.apache.solr.handler.RequestHandlerBase.handleRequest(
> 	at org.apache.solr.core.SolrCore.execute(
> 	at org.apache.solr.servlet.SolrDispatchFilter.execute(
> 	at org.apache.solr.servlet.SolrDispatchFilter.doFilter(
> 	at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(
> 	at org.mortbay.jetty.servlet.ServletHandler.handle(
> 	at
> 	at org.mortbay.jetty.servlet.SessionHandler.handle(
> 	at org.mortbay.jetty.handler.ContextHandler.handle(
> 	at org.mortbay.jetty.webapp.WebAppContext.handle(
> 	at org.mortbay.jetty.handler.ContextHandlerCollection.handle(
> 	at org.mortbay.jetty.handler.HandlerCollection.handle(
> 	at org.mortbay.jetty.handler.HandlerWrapper.handle(
> 	at org.mortbay.jetty.Server.handle(
> 	at org.mortbay.jetty.HttpConnection.handleRequest(
> 	at org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(
> 	at org.mortbay.jetty.HttpParser.parseNext(
> 	at org.mortbay.jetty.HttpParser.parseAvailable(
> 	at org.mortbay.jetty.HttpConnection.handle(
> 	at$
> 	at org.mortbay.thread.BoundedThreadPool$
> 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:
For additional commands, e-mail:

View raw message