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

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

Commit 939057deff8cbf36e9c31ffcaffed30efea372f2 in lucene-solr's branch 
refs/heads/branch_8x from Andy Vuong
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=939057d ]

SOLR-14107: Ensure bin/solr -q/-v args work with -e/example (#1093)

Co-authored-by: Andy Vuong <[email protected]>

> 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
>            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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to