[
https://issues.apache.org/jira/browse/SOLR-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829451#action_12829451
]
Lance Norskog commented on SOLR-1742:
-------------------------------------
I just tried this and the old 'pint' type works as a unique key. The
QueryElevationComponent complains and you have to turn it off, but that's all
that happened.
The type has to be set to 'pint' before you add the document.
> 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.
