[
https://issues.apache.org/jira/browse/SOLR-4760?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654393#comment-13654393
]
Erick Erickson commented on SOLR-4760:
--------------------------------------
right, I'm seeing the same thing:
sb.append(loader.getCoreProperties().getProperty(NAME));
getCoreProperties returns null here. Seems like a simple if test here would
suffice, are you taking care of it or should I? I've seen several situations
where stuff is null (particularly CoreContainer.cfg) in the test environment
that are _never_ null in non-test, this could be another one of those.
> Improve logging messages during startup to better identify core
> ---------------------------------------------------------------
>
> Key: SOLR-4760
> URL: https://issues.apache.org/jira/browse/SOLR-4760
> Project: Solr
> Issue Type: Wish
> Components: Schema and Analysis
> Affects Versions: 4.3
> Reporter: Alexandre Rafalovitch
> Priority: Minor
> Fix For: 5.0, 4.4, 4.3.1
>
> Attachments: SOLR-4760.patch, SOLR-4760.patch
>
>
> Some log messages could be more informative. For example:
> {code}
> 680 [coreLoadExecutor-3-thread-3] WARN org.apache.solr.schema.IndexSchema –
> schema has no name!
> {code}
> Would be _very nice_ to know which core this is complaining about.
> Later, once the core is loaded, the core name shows up in the logs,
> but it would be nice to have it earlier without having to
> triangulating it through 'Loading core' messages.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
