lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hoss Man (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (SOLR-1742) uniqueKey must be string type otherwise "missing core name in path" error is rendered
Date Thu, 04 Feb 2010 19:53:29 GMT

     [ 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.


Mime
View raw message