You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Lars Kotthoff (JIRA)" <ji...@apache.org> on 2008/04/03 04:42:24 UTC
[jira] Created: (SOLR-528) Given but undefined default search field
in schema.xml causes cryptic error message
Given but undefined default search field in schema.xml causes cryptic error message
-----------------------------------------------------------------------------------
Key: SOLR-528
URL: https://issues.apache.org/jira/browse/SOLR-528
Project: Solr
Issue Type: Improvement
Environment: Tomcat 5.5
Reporter: Lars Kotthoff
Priority: Minor
When a default search field is given in schema.xml but the field itself is not defined, a generic SolrException with the message "Schema parsing failed" is thrown. Only further down in the stacktrace the message "unknown field 'foobar'" appears (and does not indicate where the unknown field is referenced).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-528) Given but undefined default search field
in schema.xml causes cryptic error message
Posted by "Lars Kotthoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Kotthoff updated SOLR-528:
-------------------------------
Affects Version/s: 1.3
> Given but undefined default search field in schema.xml causes cryptic error message
> -----------------------------------------------------------------------------------
>
> Key: SOLR-528
> URL: https://issues.apache.org/jira/browse/SOLR-528
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Environment: Tomcat 5.5
> Reporter: Lars Kotthoff
> Priority: Minor
> Attachments: solr-default-search.patch
>
>
> When a default search field is given in schema.xml but the field itself is not defined, a generic SolrException with the message "Schema parsing failed" is thrown. Only further down in the stacktrace the message "unknown field 'foobar'" appears (and does not indicate where the unknown field is referenced).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-528) Given but undefined default search
field in schema.xml causes cryptic error message
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-528.
---------------------------
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Hoss Man
Thanks Lars...
Committed revision 646135.
> Given but undefined default search field in schema.xml causes cryptic error message
> -----------------------------------------------------------------------------------
>
> Key: SOLR-528
> URL: https://issues.apache.org/jira/browse/SOLR-528
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Environment: Tomcat 5.5
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 1.3
>
> Attachments: solr-default-search.patch
>
>
> When a default search field is given in schema.xml but the field itself is not defined, a generic SolrException with the message "Schema parsing failed" is thrown. Only further down in the stacktrace the message "unknown field 'foobar'" appears (and does not indicate where the unknown field is referenced).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-528) Given but undefined default search field
in schema.xml causes cryptic error message
Posted by "Lars Kotthoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Kotthoff updated SOLR-528:
-------------------------------
Attachment: solr-default-search.patch
Patch to create a more specific error message, i.e. "default search field 'foobar' not defined or not indexed" when raising the SolrException.
> Given but undefined default search field in schema.xml causes cryptic error message
> -----------------------------------------------------------------------------------
>
> Key: SOLR-528
> URL: https://issues.apache.org/jira/browse/SOLR-528
> Project: Solr
> Issue Type: Improvement
> Environment: Tomcat 5.5
> Reporter: Lars Kotthoff
> Priority: Minor
> Attachments: solr-default-search.patch
>
>
> When a default search field is given in schema.xml but the field itself is not defined, a generic SolrException with the message "Schema parsing failed" is thrown. Only further down in the stacktrace the message "unknown field 'foobar'" appears (and does not indicate where the unknown field is referenced).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SOLR-528) Given but undefined default search field
in schema.xml causes cryptic error message
Posted by "Lars Kotthoff (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Kotthoff closed SOLR-528.
------------------------------
> Given but undefined default search field in schema.xml causes cryptic error message
> -----------------------------------------------------------------------------------
>
> Key: SOLR-528
> URL: https://issues.apache.org/jira/browse/SOLR-528
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.3
> Environment: Tomcat 5.5
> Reporter: Lars Kotthoff
> Assignee: Hoss Man
> Priority: Minor
> Fix For: 1.3
>
> Attachments: solr-default-search.patch
>
>
> When a default search field is given in schema.xml but the field itself is not defined, a generic SolrException with the message "Schema parsing failed" is thrown. Only further down in the stacktrace the message "unknown field 'foobar'" appears (and does not indicate where the unknown field is referenced).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.