[
https://issues.apache.org/jira/browse/SOLR-14280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Gerlowski updated SOLR-14280:
-----------------------------------
Fix Version/s: 8.6
master (9.0)
Assignee: Jason Gerlowski
Resolution: Fixed
Status: Resolved (was: Patch Available)
Thanks for the improvements Andras. Committed this to master and branch_8x, so
we'll see it starting in 8.6.
FYI - no need to give your patches "version" suffixes ({{-02.patch}},
{{-01.patch}}, etc.) JIRA already handles this pretty well - attachments with
the same name are displayed in descending order, and all but the newest version
are "greyed" out to make it clear they're less-recent. (I don't mind the
suffixes, but some do, so just wanted to give you a heads up.)
> SolrConfig logging not helpful
> ------------------------------
>
> Key: SOLR-14280
> URL: https://issues.apache.org/jira/browse/SOLR-14280
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andras Salamon
> Assignee: Jason Gerlowski
> Priority: Minor
> Fix For: master (9.0), 8.6
>
> Attachments: SOLR-14280-01.patch, SOLR-14280-02.patch, getmessages.txt
>
>
> SolrConfig prints out a warning message if it's not able to add files to the
> classpath, but this message is not too helpful:
> {noformat}
> o.a.s.c.SolrConfig Couldn't add files from
> /opt/cloudera/parcels/CDH-7.1.1-1.cdh7.1.1.p0.1850855/lib/solr/dist filtered
> by solr-langid-\d.*\.jar to classpath:
> /opt/cloudera/parcels/CDH-7.1.1-1.cdh7.1.1.p0.1850855/lib/solr/
> dist {noformat}
> The reason should be at the end of the log message but it's just repeats the
> problematic file name.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
