lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Grant Ingersoll (JIRA)" <>
Subject [jira] Commented: (SOLR-1309) Exception thrown by debugging component after phonetic filter parses numeric query, BUG?
Date Mon, 03 Aug 2009 23:01:14 GMT


Grant Ingersoll commented on SOLR-1309:

I added:
<field name="namePhonetic" type="phonetic" indexed="true" stored="false"/>
to the example, along with copyField.  I then re-indexed and then did:

But didn't get any exceptions, although the parsed query is indeed empty, so I think this
is fixed in trunk.

> Exception thrown by debugging component after phonetic filter parses numeric query, BUG?
> ----------------------------------------------------------------------------------------
>                 Key: SOLR-1309
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: Analysis
>    Affects Versions: 1.3
>         Environment: Redhat 5.3 Enterprise x64.   (latest)  running Ludid Imagination
1.30 release 
>            Reporter: Robert Petersen
>            Priority: Minor
>             Fix For: 1.4
> It certainly looks like a bug - definitely in QueryParsing.toString() and perhaps with
the phonetic filter for producing a zero length term?  Please do open a bug and target to
> -Yonik
> Here is my bug description:
> Exception thrown by debugging component when query hits phonetic filter factory with
a numeric term no matter what kind of phonetic filter is selected.  I am reposting with this
new subject line thinking this is a potential issue which possibly needs addressing in future
releases and should be submitted as a BUG?    It must be getting an empty field object from
the phonetic filter factory for numeric terms or something similar.
> Jul 23, 2009 2:58:17 PM org.apache.solr.core.SolrCore execute
> INFO: [10017] webapp=/solr path=/select/ params={debugQuery=true&rows=10&start=0&q=((((allDoublemetaphone:"2343")^0.5)))}
hits=6873 status=500 QTime=3 
> Jul 23, 2009 2:58:17 PM org.apache.solr.common.SolrException log
> SEVERE: java.lang.RuntimeException: java.lang.IllegalArgumentException: name and value
cannot both be empty
> 	at
> 	at org.apache.solr.util.SolrPluginUtils.doStandardDebug(
> 	at org.apache.solr.handler.component.DebugComponent.process(
> 	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.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> 	at org.apache.catalina.core.StandardWrapperValve.invoke(
> 	at org.apache.catalina.core.StandardContextValve.invoke(
> 	at org.apache.catalina.core.StandardHostValve.invoke(
> 	at org.apache.catalina.valves.ErrorReportValve.invoke(
> 	at org.apache.catalina.core.StandardEngineValve.invoke(
> 	at org.apache.catalina.connector.CoyoteAdapter.service(
> 	at org.apache.coyote.http11.Http11Processor.process(
> 	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(
> 	at$
> 	at
> Caused by: java.lang.IllegalArgumentException: name and value cannot both be empty
> 	at org.apache.lucene.document.Field.<init>(
> 	at org.apache.lucene.document.Field.<init>(
> 	at
> 	at
> 	at
> 	... 19 more

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

View raw message