lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <>
Subject [jira] Resolved: (SOLR-1171) dynamic field name with spaces causes error
Date Thu, 09 Jul 2009 23:56:15 GMT


Hoss Man resolved SOLR-1171.

    Resolution: Fixed
      Assignee: Hoss Man

This bug was even more heinous then it seems at first blush ... if you use dynamic fields
with a *suffix* it failed silently, giving you a bogus doc count.  A field name like "name
with spaces_t" resulted in a query for "name with spaces_t:[* TO *]" which would give you
the count of docs with a value in the "spaces_t" field *or* contained "name" or "with" in
the defaultSearchField.

Committed revision 792751.

> dynamic field name with spaces causes error
> -------------------------------------------
>                 Key: SOLR-1171
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Ryan McKinley
>            Assignee: Hoss Man
>             Fix For: 1.4
> Stumbled into this bug.  I have a dynamic field "meta_set_*"  When I add the field: 
"meta_set_NoData Value" and try to open luke, I get this exception:
> {panel}
> May 15, 2009 3:42:06 PM org.apache.solr.common.SolrException log
> SEVERE: org.apache.solr.common.SolrException: undefined field Value
> 	at org.apache.solr.schema.IndexSchema.getDynamicFieldType(
> 	at org.apache.solr.schema.IndexSchema.getFieldType(
> 	at
> 	at org.apache.lucene.queryParser.QueryParser.Term(
> 	at org.apache.lucene.queryParser.QueryParser.Clause(
> 	at org.apache.lucene.queryParser.QueryParser.Query(
> 	at org.apache.lucene.queryParser.QueryParser.TopLevelQuery(
> 	at org.apache.lucene.queryParser.QueryParser.parse(
> 	at org.apache.solr.handler.admin.LukeRequestHandler.getIndexedFieldsInfo(
> 	at org.apache.solr.handler.admin.LukeRequestHandler.handleRequestBody(
> 	at org.apache.solr.handler.RequestHandlerBase.handleRequest(
> 	at org.apache.solr.core.SolrCore.execute(
> {panel}
> note the field is "meta_set_gdal_NoData Value" not "Value"
> I think the query parser is grabbing it...

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

View raw message