REPLACE implements eval function to replace part of a string.
A = load 'mydata' as (name);
B = foreach A generate REPLACE(name, 'blabla', 'bla');
The first argument is a string on which to perform the operation. The second argument
is treated as a regular expression. The third argument is the replacement string.
This is a wrapper around Java's String.replaceAll(String, String);
Nested Class Summary
Nested classes/interfaces inherited from class org.apache.pig.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.
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
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.
Whether the UDF should be evaluated at compile time if all inputs are constant.
This is applicable for most UDF, however, if a UDF will access hdfs file which
is not available at compile time, it has to be false