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 2010/02/04 20:53:29 UTC
[jira] Resolved: (SOLR-1742) uniqueKey must be string type
otherwise "missing core name in path" error is rendered
[ https://issues.apache.org/jira/browse/SOLR-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-1742.
----------------------------
Resolution: Duplicate
the string dependency for QueryElevationComponent does seem to be the root of the problem -- i think we should try to get the the bottom of why such a confusing error message is reported, but we've already got SOLR-1743 to track that.
> uniqueKey must be string type otherwise "missing core name in path" error is rendered
> -------------------------------------------------------------------------------------
>
> Key: SOLR-1742
> URL: https://issues.apache.org/jira/browse/SOLR-1742
> Project: Solr
> Issue Type: Bug
> Components: Build
> Environment: all
> Reporter: Marcin
> Fix For: 1.5
>
>
> How to replicate:
> - create index with schema where you uniqueKet is integer
> - set your unique key type to integer
> - deploy your index
> under http://host:8080/solr/admin/ - you will get "missing core name in path"
> Workaround:
> - change type of your uniqueKet to srting
> - undeploy and deploy index
> Its quite confusing as 1.5 is not properly reporting errors and you need to be lucky to find that reason on your own.
> cheers,
> /Marcin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.