[
https://issues.apache.org/jira/browse/SOLR-2231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Fuad Efendi updated SOLR-2231:
------------------------------
Description:
Please use
{code}
if (LOG.isInfoEnabled()) LOG.info(...)
{code}
For instance, line 95 of ThreadedEntityProcessorWrapper creates huge log output
which is impossible to manage via logging properties:
LOG.info("arow : "+arow);
This line (in a loop) will output results of all SQL from a database (and will
slow down SOLR performance). It's even better to use LOG.debug instead of
LOG.info, INFO is enabled by default.
was:
Please use
{code}
if (LOG.isInfoEnabled()) LOG.info(...)
{code}
For instance, line 95 of ThreadedEntityProcessorWrapper creates huge log output
which is impossible to manage via logging properties:
LOG.info("arow : "+arow);
> DataImportHandler - MultiThreaded - Logging
> -------------------------------------------
>
> Key: SOLR-2231
> URL: https://issues.apache.org/jira/browse/SOLR-2231
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 1.5
> Reporter: Fuad Efendi
> Priority: Trivial
>
> Please use
> {code}
> if (LOG.isInfoEnabled()) LOG.info(...)
> {code}
> For instance, line 95 of ThreadedEntityProcessorWrapper creates huge log
> output which is impossible to manage via logging properties:
> LOG.info("arow : "+arow);
> This line (in a loop) will output results of all SQL from a database (and
> will slow down SOLR performance). It's even better to use LOG.debug instead
> of LOG.info, INFO is enabled by default.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
