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

Shawn Heisey commented on SOLR-2646:
------------------------------------

bq. I know very little about logging, but shouldn't jcl-over-slf4j-*.jar be 
used here? I think its job is to intercept commons-logging calls and then slf4j 
will push them through wherever it's configured to go (log4j by default I 
think).

I don't know if the commons-logging classes are actually used (indirectly) by 
SolrJ ... but if they are, this is a possibly sticky problem because SolrJ 
itself uses SLF4J.  Whether to use the commons-logging or jcl-over-slf4j jar 
depends on which slf4j binding the final application will use.  If the user 
binds slf4j to jcl with slf4j-jcl, then they need the actual commons-logging 
jar.  If the user chooses any other binding, jcl-over-slf4j is required.  We 
can't make that choice for the user, which I think means that the SolrJ 
documentation must explain these details.


> Integrate Solr benchmarking support into the Benchmark module
> -------------------------------------------------------------
>
>                 Key: SOLR-2646
>                 URL: https://issues.apache.org/jira/browse/SOLR-2646
>             Project: Solr
>          Issue Type: New Feature
>            Reporter: Mark Miller
>         Attachments: Dev-SolrBenchmarkModule.pdf, SOLR-2646.patch, 
> SOLR-2646.patch, SOLR-2646.patch, SOLR-2646.patch, SOLR-2646.patch, 
> SOLR-2646.patch, SOLR-2646.patch, SOLR-2646.patch, 
> SolrIndexingPerfHistory.pdf, chart.jpg
>
>
> As part of my buzzwords Solr pef talk, I did some work to allow some Solr 
> benchmarking with the benchmark module.
> I'll attach a patch with the current work I've done soon - there is still a 
> fair amount to clean up and fix - a couple hacks or three - but it's already 
> fairly useful.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to