[ 
https://issues.apache.org/jira/browse/SOLR-9534?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514532#comment-15514532
 ] 

ASF subversion and git services commented on SOLR-9534:
-------------------------------------------------------

Commit bede7aefa3b2294e869d7fa543417e160e3518f9 in lucene-solr's branch 
refs/heads/master from [~janhoy]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=bede7ae ]

SOLR-9534: Fix test failures related to nullpointer when printing core name in 
logs.


> Support quiet/verbose bin/solr options for changing log level
> -------------------------------------------------------------
>
>                 Key: SOLR-9534
>                 URL: https://issues.apache.org/jira/browse/SOLR-9534
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: scripts and tools
>    Affects Versions: 6.2
>            Reporter: Jan Høydahl
>            Assignee: Jan Høydahl
>              Labels: logging
>             Fix For: 6.3, master (7.0)
>
>         Attachments: SOLR-9534.patch, SOLR-9534.patch
>
>
> Spinoff from SOLR-6677
> Let's make it much easier to "turn on debug" by supporting a {{bin/solr start 
> -V}} verbose option, and likewise a {{bin/solr start -q}} for quiet operation.
> These would simply be convenience options for changing the RootLogger from 
> level INFO to DEBUG or WARN respectively. This can be done programmatically 
> in log4j at startup. 
> Could be we need to add some more package specific defaults in 
> log4j.properties to get the right mix of logs



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to