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 "Hoss Man (JIRA)" <ji...@apache.org> on 2009/11/12 21:02:39 UTC
[jira] Created: (SOLR-1558) QueryElevationComponent should fail to
init if uniqueKey field isn't string
QueryElevationComponent should fail to init if uniqueKey field isn't string
---------------------------------------------------------------------------
Key: SOLR-1558
URL: https://issues.apache.org/jira/browse/SOLR-1558
Project: Solr
Issue Type: Bug
Components: search
Affects Versions: 1.4, 1.3
Reporter: Hoss Man
Fix For: 1.5
QueryElevationComponent fails in confusing ways if you use it on a schema where the uniqueKey fieldtype is not a StrField. This is easy to assert at init, so we should do that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-1558) QueryElevationComponent should fail to
init if uniqueKey field isn't string
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-1558.
----------------------------
Resolution: Fixed
Assignee: Hoss Man
Committed revision 884393.
Note that the code change only required modifying two lines, but this fix exposed 7 test config files that had cut/paste declaations of the elevation component that weren't used, and never would have worked because of the schema used in the tests.
> QueryElevationComponent should fail to init if uniqueKey field isn't string
> ---------------------------------------------------------------------------
>
> Key: SOLR-1558
> URL: https://issues.apache.org/jira/browse/SOLR-1558
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.3, 1.4
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 1.5
>
>
> QueryElevationComponent fails in confusing ways if you use it on a schema where the uniqueKey fieldtype is not a StrField. This is easy to assert at init, so we should do that.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.