[
https://issues.apache.org/jira/browse/SOLR-12987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated SOLR-12987:
--------------------------------
Description:
Added {{org.apache.solr.logging.DeprecationLog}}. Up to the user to configure
logging to go to a separate file if they wish.
Old description:
----
As discussed in solr-user list:
{quote}When instructing people in what to do before upgrading to a new version,
we often tell them to check for deprecation log messages and fix those before
upgrading. Normally you'll see the most important logs as WARN level in the
Admin UI log tab just after startup and first use. But I'm wondering if it also
makes sense to introduce a separate DeprecationLogger.log(foo) that is
configured in log4j2.xml to log to a separate logs/deprecation.log to make it
easier to check this from the command line. If the file is non-empty you have
work to do :)
{quote}
was:
As discussed in solr-user list:
{quote}When instructing people in what to do before upgrading to a new version,
we often tell them to check for deprecation log messages and fix those before
upgrading. Normally you'll see the most important logs as WARN level in the
Admin UI log tab just after startup and first use. But I'm wondering if it also
makes sense to introduce a separate DeprecationLogger.log(foo) that is
configured in log4j2.xml to log to a separate logs/deprecation.log to make it
easier to check this from the command line. If the file is non-empty you have
work to do :)
{quote}
Summary: Utility to log deprecation warnings (was: Log deprecation
warnings to separate log file)
> Utility to log deprecation warnings
> -----------------------------------
>
> Key: SOLR-12987
> URL: https://issues.apache.org/jira/browse/SOLR-12987
> Project: Solr
> Issue Type: New Feature
> Components: logging
> Reporter: Jan Høydahl
> Assignee: David Smiley
> Priority: Major
> Fix For: 8.7
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Added {{org.apache.solr.logging.DeprecationLog}}. Up to the user to
> configure logging to go to a separate file if they wish.
> Old description:
> ----
> As discussed in solr-user list:
> {quote}When instructing people in what to do before upgrading to a new
> version, we often tell them to check for deprecation log messages and fix
> those before upgrading. Normally you'll see the most important logs as WARN
> level in the Admin UI log tab just after startup and first use. But I'm
> wondering if it also makes sense to introduce a separate
> DeprecationLogger.log(foo) that is configured in log4j2.xml to log to a
> separate logs/deprecation.log to make it easier to check this from the
> command line. If the file is non-empty you have work to do :)
> {quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
