[jira] [Assigned] (SOLR-14107) Allow solr cli run tool to use quiet or verbose log levels

["Jason Gerlowski (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-14107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Gerlowski reassigned SOLR-14107:
--------------------------------------

    Assignee: Jason Gerlowski

> Allow solr cli run tool to use quiet or verbose log levels
> ----------------------------------------------------------
>
>                 Key: SOLR-14107
>                 URL: https://issues.apache.org/jira/browse/SOLR-14107
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: SolrCloud
>            Reporter: Andy Vuong
>            Assignee: Jason Gerlowski
>            Priority: Trivial
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Trivial fix
> According to the solr control script reference (
> [https://lucene.apache.org/solr/guide/8_3/solr-control-script-reference.html#solr-control-script-reference])
> , passing -v changes the logging level of log4j from INFO to DEBUG. This isn’t the case when used with any of the examples passing -e. I frequently use a command like
> _bin/solr start -e cloud -noprompt_
> to spin up a quick 2 node cluster and would’ve expected -v to enable debug.
> This is a trivial patch to allow the examples to run with DEBUG (likewise WARN for -q): 
>  _bin/solr start -e cloud -noprompt -v_
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org