LogLevel:SL,SC-EL,EC: messageWhere SL, SC - line and column where issue start, EL,EC line and column where issue ends.
A simple logging interface abstracting logging APIs. In order to be instantiated successfully by {@link LogFactory}, classes that implement this interface must have a constructor that takes a single String parameter representing the "name" of this Log.
The six logging levels used by Log are (in order):
Performance is often a logging concern. By examining the appropriate property, a component can avoid expensive operations (producing information to be logged).
For example, if (log.isDebugEnabled()) { ... do something expensive ... log.debug(theResult); }
Configuration of the underlying logging system will generally be done external to the Logging APIs, through whatever mechanism is supported by that system.
Please note that this interface is identical to that found in JCL 1.1.1.
@author Scott Sanders @author Rod Waldhoff @version $Id: Log.java,v 1.19 2004/06/06 21:16:04 rdonkin Exp $This is NOT part of any supported API. If you write code that depends on this, you do so at your own risk. This code and its internal interfaces are subject to change or deletion without notice.
Thank you for your selection of using our component.
Copyright: Copyright (c) 2009 Thousand Origami Cranes Corp.
Create Time: 25 Dec 2009 19:21:57 @author Kevin.Zhou @version 1.0 @see com.toc.logging.Configuration
A simple logging interface abstracting logging APIs. In order to be instantiated successfully by {@link LogFactory}, classes that implement this interface must have a constructor that takes a single String parameter representing the "name" of this Log.
The six logging levels used by Log are (in order):
Performance is often a logging concern. By examining the appropriate property, a component can avoid expensive operations (producing information to be logged).
For example, if (log.isDebugEnabled()) { ... do something expensive ... log.debug(theResult); }
Configuration of the underlying logging system will generally be done external to the Logging APIs, through whatever mechanism is supported by that system.
@author Scott Sanders @author Rod WaldhoffA simple logging interface abstracting logging APIs. In order to be instantiated successfully by {@link LogFactory}, classes that implement this interface must have a constructor that takes a single String parameter representing the "name" of this Log.
The six logging levels used by Log are (in order):
Performance is often a logging concern. By examining the appropriate property, a component can avoid expensive operations (producing information to be logged).
For example, if (log.isDebugEnabled()) { ... do something expensive ... log.debug(theResult); }
Configuration of the underlying logging system will generally be done external to the Logging APIs, through whatever mechanism is supported by that system.
@author Scott Sanders @author Rod WaldhoffDoxia channels. java.lang.CharSequence rather than java.lang.String. This is provided mainly as a convenience, to enable developers to pass things like java.lang.StringBuilder directly into the logger, rather than formatting first by calling toString(). org.apache.maven.plugin.logging.Log.
@author jdcasey
@author ltheussl
@version $Id: Log.java 1438269 2013-01-24 23:47:50Z olamy $
@since 1.1
value - DataAtom [double].DataAtom [double] register math.jar;
A = load 'mydata' using PigStorage() as ( float1 );
B = foreach A generate float1, math.LOG(float1); if (LOG.e()) LOG.a( "Value is: ").a( value ).lf();and, for nested scopes,
if (LOG.e()) LOG.a( "Entering" ).lf().i(); ... if (LOG.e()) LOG.o().a( "Leaving" ).lf();@author peo
Log log = LogFactory.getLog( getClass() ); The above will get you an instance of Log, which can be used to generate log messages either via JBoss Logging which then can delegate to Log4J (if the libraries are present) or (if not) the built-in JDK logger. In addition to the 6 log levels available, this framework also supports parameter interpolation, similar to the JDKs {@link String#format(String,Object)}method. What this means is, that the following block: if (log.isTraceEnabled()) { log.trace("This is a message " + message + " and some other value is " + value); } ... could be replaced with ... if (log.isTraceEnabled()) log.tracef("This is a message %s and some other value is %s", message, value); This greatly enhances code readability. If you are passing a Throwable, note that this should be passed in before the vararg parameter list.
@author Manik Surtani
@since 4.0
Every Log has a verboselevel associated with it; any log request with loglevel less or equal to the verbose-level is logged.
Verbose level 0 indicates no log. The log levels should be greater than 0.
Parameter logname, if non-null, is used as log header (i.e. written at the begin of each log row).
| |
| |
| |
| |
| |
| |
| |
| |
| |