lucene-solr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (SOLR-1742) uniqueKey must be string type otherwise "missing core name in path" error is rendered
Date Thu, 04 Feb 2010 14:16:28 GMT

    [ https://issues.apache.org/jira/browse/SOLR-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829607#action_12829607
] 

Mark Miller edited comment on SOLR-1742 at 2/4/10 2:15 PM:
-----------------------------------------------------------

Hey Marcin,

You should be able to use int (or sint) no problem. When you see the error "missing core name
in path", thats often an indication you need to check your logs (especially if you are running
single core) - look for the first error, timewise, that you can find. In this case you will
see: the QueryElevationComponent requires a String id field. If you remove the QueryElevationComponent/Handler,
you should no longer see "missing core name in path" and Solr will start up.

- Mark

      was (Author: markrmiller@gmail.com):
    Hey Marcin,

You should be able to use int no problem. When you see the error "missing core name in path",
thats often an indication you need to check your logs (especially if you are running single
core) - look for the first error, timewise, that you can find. In this case you will see:
the QueryElevationComponent requires a String id field. If you remove the QueryElevationComponent/Handler,
you should no longer see "missing core name in path" and Solr will start up.

- Mark
  
> 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