[
https://issues.apache.org/jira/browse/SOLR-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14181281#comment-14181281
]
Jan Høydahl edited comment on SOLR-6647 at 10/23/14 12:28 PM:
--------------------------------------------------------------
New patch using new static method {{CloudUtil#unifiedResourcePath(loader)}}.
This will return the getCollectionZkPath if in ZK mode.
I think it is dangerous to support getConfigDir in ZK loader, as the typical
error is to assume that this method returns a valid File-system path, which we
can never do from ZK.
And I think we should create another JIRA to handle all other places where
there is unsafe usage of getConfigDir. I have spotted a few already...
was (Author: janhoy):
New patch using new static method {{CloudUtil#unifiedResourcePath(loader)}}.
This will return the getCollectionZkPath if in ZK mode.
I think it is dangerous to support getConfigDir in ZK loader, as the typical
error is to assume that this method returns a valid File-system path, which we
can never do from ZK.
> Bad error message when missing resource from ZK when parsing Schema
> -------------------------------------------------------------------
>
> Key: SOLR-6647
> URL: https://issues.apache.org/jira/browse/SOLR-6647
> Project: Solr
> Issue Type: Bug
> Components: Schema and Analysis
> Affects Versions: 4.10.1
> Reporter: Jan Høydahl
> Fix For: 4.10.2, 5.0, Trunk
>
> Attachments: SOLR-6647.patch, SOLR-6647.patch
>
>
> Creating a collection via Collection API. Schema points to a file which is
> not in our config folder in ZooKeeper. Getting the infamous error message
> {{ZkSolrResourceLoader does not support getConfigDir()}} instead of the more
> helpful message about which resource is missing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
