CloverETL wiki

running

mildredschaefer — 2010-02-26T15:01:26+01:00

We assume that you have downloaded a binary package of CloverETL framework and Clover Examples or you have built one from sources. Extract the examples to the engine directory. Thus, if you have your engine in the pathtoyourengine/cloverETL/ directory, after extracting the examples to this directory, it will contain the following subdirectories: bin/, docs/, examples/, lib/ and plugins/. The examples can be found in the examples/ subdirectory.

transformation_concept - added graph XML schema to ToC

Martin Zatopek — 2010-02-25T14:43:49+01:00

Transformation graph (further referred to only as graph) describes how to transform data from one form to another. Graph consists of at least three elements, Nodes (perform various simple transformations), Edges (connect Nodes and pass data around) and Metadata (describe data structure that is defined at every Nodes and Edges).

graph_xml_schema - flesh out article

Martin Zatopek — 2010-02-25T14:41:45+01:00

This file was created to allow you to test if a CloverETL graph is valid or not. You can find several XSD validators online or write your own in Java (or Perl, Python, C++, etc.). This file should be correct for 99% of graphs, but there may be some bugs. When you validate with this file, you must specify that the graph is in the CloverETL namespace by specifying the xmlns attribute in the Graph element:

start

Maikl Paterson — 2010-02-25T13:33:48+01:00

CloverETL is a Java based ETL framework which can be used to transform structured data, and to some degree free-form data. Its complete platform independence is achieved by the exclusive use of Java technology. It can be used standalone as an application launched from a command line or can be embedded into your own application. CloverETL is released under the LGPL license.

components:readers

Jan Ausperger — 2010-02-18T16:47:06+01:00

Readers are initial components of graph that reads data from input source. The source can be for example a file placed on local disk, ftp, ldap, jms or database tables, etc. Graph must contain at least one of these components or more. ----------

embedding_clover

David Pavlis — 2010-02-16T15:30:13+01:00

The TransformationGraph class Transformation graph is both abstraction and class which performs some operation. Graph keeps track of all Nodes, Edges, metadata objects. It is also accompanied by class which enables reading the definition of graph from XML file and building everything dynamically.

components:writers

Jan Ausperger — 2010-02-12T10:14:01+01:00

Writers are terminated components of graph that writes data to output source. The source can be for example a file placed on local disk, ftp, ldap, jms or database tables, etc. Graph must contain at least one of these components or more. ----------

components:transformers

Agata Vackova — 2010-02-04T11:21:34+01:00

Transformers are components of graph that transform data from one or more input ports to output port. Most of transformers use transform function or key or some other method that defines particular data transformation. Note: For characters that are impossible to enter directly, there are several escape sequences: \\, \n, \t, \r, \”, \f, \b. So be careful when using “\” character, eg. parameter filterExpression=“$Field1~="([^\\|]*\\|){3}"” will be interpreted as “$Field1~="([^\|]…

components:bulkloaders:infobright_data_writer

Agata Vackova — 2010-01-29T11:03:20+01:00

since 2.9 version This component loads data to Infobright database. It supports local load, as well as, the remote one. If the hostname is “localhost” or “127.0.0.1” then the load will be done using a local pipe. Otherwise it will use a remote pipe. The external IP address of the server is not recognized as a local server. If loading to a remote server, then you need to start the Infobright remote load agent on the server where Infobright is running. The command to do this is: java -jar infobr…