org.apache.pig.piggybank.evaluation.util.apachelogparser

Class SearchTermExtractor

java.lang.Object

org.apache.pig.EvalFunc<String>

org.apache.pig.piggybank.evaluation.util.apachelogparser.SearchTermExtractor

public class SearchTermExtractor
extends EvalFunc<String>

SearchTermExtractor takes a url string and extracts the search terms. For example, given http://www.google.com/search?hl=en&safe=active&rls=GGLG,GGLG:2005-24,GGLG:en&q=purpose+of+life&btnG=Search then purpose of life would be extracted. From pig latin, usage looks something like searchTerm = FOREACH row GENERATE org.apache.pig.piggybank.evaluation.util.apachelogparser.SearchTermExtractor(referer); Supported search engines include alltheweb.com, altavista.com, aolsearch.aol.com, arianna.libero.it, as.starware.com, ask.com, blogs.icerocket.com, blueyonder.co.uk, busca.orange.es, buscador.lycos.es, buscador.terra.es, buscar.ozu.es, categorico.it, cerca.lycos.it, cuil.com, excite.it, godado.com, godado.it, gps.virgin.net, hotbot.com, ilmotore.com, it.altavista.com, ithaki.net, libero.it, lycos.es, lycos.it, mamma.com, megasearching.net, mirago.co.uk, netscape.com, ozu.es, ricerca.alice.it, search.aol.co.uk, search.bbc.co.uk, search.conduit.com, search.icq.com, search.live.com, search.lycos.co.uk, search.lycos.com, search.msn.co.uk, search.msn.com, search.myway.com, search.mywebsearch.com, search.ntlworld.com, search.orange.co.uk, search.sweetim.com, search.virginmedia.com, simpatico.ws, soso.com, suche.fireball.de, suche.web.de, terra.es, tesco.net, thespider.it, tiscali.co.uk, uk.altavista.com, uk.ask.com Thanks to Spiros Denaxas for his URI::ParseSearchString, which is the basis for the lookups.

Nested Class Summary

Nested classes/interfaces inherited from class org.apache.pig.EvalFunc

EvalFunc.SchemaType

Field Summary

Fields inherited from class org.apache.pig.EvalFunc

log, pigLogger, reporter, returnType

Constructor Summary

Constructors

Constructor and Description
SearchTermExtractor()

Method Summary

Modifier and Type	Method and Description
String	exec(Tuple input) This callback method must be implemented by all subclasses.
List<FuncSpec>	getArgToFuncMapping() Allow a UDF to specify type specific implementations of itself.

Methods inherited from class org.apache.pig.EvalFunc

allowCompileTimeCalculation, finish, getCacheFiles, getInputSchema, getLoadCaster, getLogger, getPigLogger, getReporter, getReturnType, getSchemaName, getSchemaType, getShipFiles, isAsynchronous, needEndOfAllInputProcessing, outputSchema, progress, setEndOfAllInput, setInputSchema, setPigLogger, setReporter, setUDFContextSignature, warn

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

SearchTermExtractor

public SearchTermExtractor()

Method Detail

exec

public String exec(Tuple input)
            throws IOException

Description copied from class: EvalFunc

This callback method must be implemented by all subclasses. This is the method that will be invoked on every Tuple of a given dataset. Since the dataset may be divided up in a variety of ways the programmer should not make assumptions about state that is maintained between invocations of this method.

Specified by:

exec in class EvalFunc<String>

Parameters:

input - the Tuple to be processed.

Returns:

result, of type T.

Throws:

IOException

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<String>

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:

1. FuncSpec(this.getClass().getName(), new Schema(new Schema.FieldSchema(null, DataType.DOUBLE)))
2. 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