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 "Marcin (JIRA)" <ji...@apache.org> on 2010/02/01 12:09:50 UTC
[jira] Created: (SOLR-1742) uniqueKey must be string type otherwise
"missing core name in path" error is rendered
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.
[jira] Issue Comment Edited: (SOLR-1742) uniqueKey must be string
type otherwise "missing core name in path" error is rendered
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (SOLR-1742) uniqueKey must be string type
otherwise "missing core name in path" error is rendered
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SOLR-1742) uniqueKey must be string type
otherwise "missing core name in path" error is rendered
Posted by "Marcin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830048#action_12830048 ]
Marcin commented on SOLR-1742:
------------------------------
OK guys, thanks for that. I am closing this issue then and looking forward to solve SOLR-1743 now.
cheers,
/Marcin
> 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.
[jira] Commented: (SOLR-1742) uniqueKey must be string type
otherwise "missing core name in path" error is rendered
Posted by "Marcin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829586#action_12829586 ]
Marcin commented on SOLR-1742:
------------------------------
Cool, but what If I would like to be able to sort on it since sint is not working its not really solving my issue.
/cheers
> 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.
[jira] Closed: (SOLR-1742) uniqueKey must be string type otherwise
"missing core name in path" error is rendered
Posted by "Marcin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marcin closed SOLR-1742.
------------------------
> 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.
[jira] Commented: (SOLR-1742) uniqueKey must be string type
otherwise "missing core name in path" error is rendered
Posted by "Lance Norskog (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (SOLR-1742) uniqueKey must be string type
otherwise "missing core name in path" error is rendered
Posted by "Mark Miller (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829607#action_12829607 ]
Mark Miller commented on SOLR-1742:
-----------------------------------
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.