org.apache.pig.builtin
Class ROUND
java.lang.Object
org.apache.pig.EvalFunc<Long>
org.apache.pig.builtin.ROUND
public class ROUND
- extends EvalFunc<Long>
ROUND implements a binding to the Java function
Math.round(double)
.
Given a single data atom it Returns the closest long to the argument.
Constructor Summary |
ROUND()
|
Methods inherited from class org.apache.pig.EvalFunc |
finish, getCacheFiles, getLogger, getPigLogger, getReporter, getReturnType, getSchemaName, isAsynchronous, progress, setPigLogger, setReporter, warn |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
ROUND
public ROUND()
exec
public Long exec(Tuple input)
throws IOException
- java level API
- Specified by:
exec
in class EvalFunc<Long>
- Parameters:
input
- expects a single numeric value
- Returns:
- output returns a single numeric value,
the closest long to the argument
- Throws:
IOException
outputSchema
public Schema outputSchema(Schema input)
- Description copied from class:
EvalFunc
- Report the schema of the output of this UDF. Pig will make use of
this in error checking, optimization, and planning. The schema
of input data to this UDF is provided.
- Overrides:
outputSchema
in class EvalFunc<Long>
- Parameters:
input
- Schema of the input
- Returns:
- Schema of the output
getArgToFuncMapping
public List<FuncSpec> getArgToFuncMapping()
throws FrontendException
- Description copied from class:
EvalFunc
- Allow a UDF to specify type specific implementations of itself. For example,
an implementation of arithmetic sum might have int and float implementations,
since integer arithmetic performs much better than floating point arithmetic. Pig's
typechecker will call this method and using the returned list plus the schema
of the function's input data, decide which implementation of the UDF to use.
- Overrides:
getArgToFuncMapping
in class EvalFunc<Long>
- Returns:
- A List containing FuncSpec objects representing the EvalFunc class
which can handle the inputs corresponding to the schema in the objects. Each
FuncSpec should be constructed with a schema that describes the input for that
implementation. For example, the sum function above would return two elements in its
list:
- FuncSpec(this.getClass().getName(), new Schema(new Schema.FieldSchema(null, DataType.DOUBLE)))
- FuncSpec(IntSum.getClass().getName(), new Schema(new Schema.FieldSchema(null, DataType.INTEGER)))
This would indicate that the main implementation is used for doubles, and the special
implementation IntSum is used for ints.
- Throws:
FrontendException
Copyright © 2012 The Apache Software Foundation