[
https://issues.apache.org/jira/browse/SOLR-15421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17348946#comment-17348946
]
David Smiley commented on SOLR-15421:
-------------------------------------
{quote}...if we accidentally create an empty config directory...
{quote}
Sounds like the root cause to me. Can that be prevented?
I don't like having _two_ exists methods; let's not do that.
Also FYI the name of the "solrconfig.xml" file is actually configurable at the
time a core is created –
[CREATE|https://nightlies.apache.org/solr/draft-guides/solr-reference-guide-8.8/coreadmin-api.html#coreadmin-create]
see "config" param but I suppose we could ignore that technicality given it's
only possible in standalone mode (I think?) and it's something that a user
could work-around if there was a requirement on solrconfig.xml existing.
> ConfigSetService.checkConfigExists accepts empty configs
> --------------------------------------------------------
>
> Key: SOLR-15421
> URL: https://issues.apache.org/jira/browse/SOLR-15421
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andras Salamon
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Both {{FileSystemConfigSetService}} and {{ZkConfigSetService}} only checks
> the existence of the directory only, if we accidentally create an empty
> config directory this method returns true, but when we try to use the configs
> to create a collection we got an error message like this:
> {noformat}
> Can't find resource 'solrconfig.xml' in classpath or '/configs/config_name',
> cwd=/path/to/lib/solr/server {noformat}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
