Deprecated

This component is deprecated. Use DataReader instead.

Parses specified input data file and broadcasts the records to all connected out ports.

Input ports: * one optional input port defined/connected (port protocol see fileURL).

Output ports:

• at least one output port defined/connected.

Xml attributes:

Note:

This reader can't read multiple character delimiters if an initial part of the delimiter is contained in data before this delimiter. Ie: Delimiter is 'delim'. Data are 'xxxd!xxxdelim'. Please use DataReader instead DelimitedDataReader while the problem will be resolved.

Example:

  <Node id="InputFile" 
        type="DELIMITED_DATA_READER"
        fileURL="/tmp/mydata.dat" 
  />
 
  <Node id="InputFile" 
        type="DELIMITED_DATA_READER"
        fileURL="/tmp/mydata.dat" 
        charset="ISO-8859-15"
        dataPolicy="Strict"
        skipFirstLine="true"
        skipRows="10"
        numRecords="100"
        trim="true"
  />

This component is deprecated. Use DataReader instead.

Parses specified fixed-length record, input data file and broadcasts the records to all connected out ports. The length of record is fixed either in bytes or in chars. Byte mode is somewhat stricter than char mode. It doesn't support record delimiters, incomplete records and skipping of leading/trailing blanks in fields.



If The Byte mode is true

Caution: If you use FixLenDataReader for reading textfiles, consider the presence of the line terminators. Line terminator is one byte long in Unix-like systems and Macintosh and two bytes long under Windows. If, for example, each line contains one record, then the last field of the record must include also the line terminator, otherwise your data cannot be read correctly.

Input ports: * one optional input port defined/connected (port protocol see fileURL).

Output ports:

• at least one output port defined/connected.

Xml attributes:

Example:

  <Node id="InputFile" type="FIXED_DATA_READER" fileURL="/tmp/mydata.dat" />
 
  <Node id="InputFile" 
        type="FIXED_DATA_READER"
        fileURL="/tmp/mydata.dat"
        charset="UTF-8"
        dataPolicy="Controlled"
        byteMode="false"
        skipLeadingBlanks="true"
        skipTrailingBlanks="true"
        skipEmpty="false"
        enableIncomplete="false"
  />

This component is deprecated. Use DataWriter instead.

All records from input port [0] are formatted with delimiter and written to specified file. Delimiters are taken from metadata specified for port[0] data flow.

Input ports:

• one input port defined/connected.

Output ports: * one optional output port defined/connected (port protocol see fileURL).

Xml attributes:

Example:

  <Node id="Writer" type="DELIMITED_DATA_WRITER" fileURL="/tmp/transfor.out"/>
 
  <Node id="Writer" 
        type="DELIMITED_DATA_WRITER"
        fileURL="/tmp/transfor.out"
        append="true"
        charset="UTF-8"
        outputFieldNames="true"
        bytesPerFile="1000000"
        recordsPerFile="10000"
        recordSkip="10"
        recordCount="100"
  />

This component is deprecated. Use DataWriter instead.

All records from input port [0] are formatted with sizes specified in metadata and written to specified file. Sizes are taken from metadata specified for port[0] data flow.

Input ports:

• one input port defined/connected.

Output ports:

• one optional output port defined/connected (port protocol see fileURL).

Xml attributes:

Example:

  <Node id="Writer" type="FIXLEN_DATA_WRITER" fileURL="/tmp/transfor.out"/>
 
  <Node id="Writer"
        type="FIXLEN_DATA_WRITER"
        fileURL="/tmp/transfor.out"
        append="true"
        charset="UTF-8"
        outputFieldNames="false"
        fieldFiller=" "
        recordFiller="."
  />

This component is deprecated. Use Filter (Ext) instead.

All records for which the filterExpression evaluates TRUE are copied from input port:0 onto output port:0. Rejected records are copied onto output port:1 (if it is connected).

It can filter on text, date, integer, numeric fields with comparison [>, <, ==, =<, >=, !=] Text fields can also be compared to a Java regexp. using ~ (tilda) character. A filter can be made of different parts separated by a ”;”. If one of the parts is verified, the record pases the filter (it's an OR combination of the parts, and AND can be achieved by several filters). Date format used for comparison is the same as defined for the field which is used for filtration.

Input ports: * 0 - input records

Output ports:

• 0 - accepted records
• 1 - (optional) rejected records

Xml attributes:

Example:

  <Node id="FILTEREMPL1" type="FILTER" filterExpression="HireDate&amp;lt;1993-12-31"/>
 
  <Node id="FILTEREMPL1" type="FILTER" filterExpression="Name~^A.*;Age>25"/>

This component is deprecated. Use Reformat instead.

This component creates key which is constructed as combination of chars from given data fields.It is possible to make some operation on original strings as removing blank space, removing diacritic, getting only alpha signs, etc.

Input ports: * one input port defined/connected.

Output ports:

• one output port defined/connected - record as on input port, but with additional field with generated key.

Xml attributes:

• keyExpression - String, which describes creating of key for each field has form: [from][-]how many[d|n|a|s|u|l]. When there is no “from” it means key is created from chars from the beginning of string or if there is ”-from” the end of string
  
  
  • Parameters:
    • d - remove diacritic (change the diacritic letters to theirs latin equivalents)<br>
    • n - get only numeric signs (checking Character.isDigit)<br>
    • a - get only alpha signs (checking Character.isLetter)<br>
    • s - remove blank space (checking Character.isWhitespace)<br>
    • u - change to upper case<br>
    • l - change to lower case

Example:

  <Node id="KEY_GEN0" type="KEY_GEN"> 
        <attr name="keyExpression">lname 2d;fname -2ad</attr>
  </Node>

This component is deprecated. Use Sort (Ext) instead.

Sorts the incoming records based on specified key. The key is name (or combination of names) of field(s) from input record.

Input ports: * one input port defined/connected.

Output ports:

• at least one output port defined/connected.

Xml attributes:

Example:

  <Node id="SORT_CUSTOMER" type="SORT" sortKey="Name:Address"/>
 
  <Node id="SORT_CUSTOMER" 
        type="SORT" 
        sortKey="Name:Address" 
        sortOrder="A"
        useI18N="true"
        locale="fr"
  />

This component is deprecated. Use HashJoin (Ext) instead.

Joins two records from two different input flows based on specified key. The flow on port 0 is the driver, the flow on port 1 is the slave. First, all records from slave flow are read and stored in hash table. Then for every record from driver flow, corresponding record from slave flow is looked up (if it exists)

Description:

Joins records on input ports. It expects driver stream at port [0] and slave streams at other input ports. Slave streams are expected to be small enough to store all the slave records in hashtable.
Each driver record is joined with corresponding slave records according to join keys specification.

• For each driver record, slave records are looked up in Hashtables which are created
• from all records on slave inputs.
• Tuple of driver and slave records is sent to transformation class.
• The method transform is called for every tuple of driver and corresponding slaves.
  

There are three join modes available: inner, left outer, full outer.

• Inner mode processess only driver records for which all associated slaves are available.
• Left outer mode furthermore processes driver records with missing slaves.

In case you use outer mode, till 2.4 version be sure your transformation code is able to handle null input records. From 2.5 version it doesn't happen any more, because for lacking record there is used special null record - all getValue methods returns null instead of throwing exception. If you want to realise some action for such record you can compare it with NullRecord.NULL_RECORD (see example below). Hash join does not require input data to be sorted. But it spends some time at the beginning initializing hashtable of slave records. It is generally good idea to specify how many records are expected to be stored in each hashtable (there is one hashtable per each slave input), especially when you expect the number to be really great. It is better to specify slightly greater number to ensure that rehashing won't occure. For small record sets - up to 512 records, there is no need to specify the size.

Input ports: * 0 - driver record input

• 1..n - slave record inputs

Output ports:

• one output port defined/connected.

Xml attributes:

Example:

  <Node id="JOIN" type="HASH_JOIN" joinKey="CustomerID" transformClass="org.jetel.test.reformatOrders"/>
 
  <Node id="JOIN" type="HASH_JOIN" joinKey="EmployeeID">
        <attr name="transform">//#TL
              function transform(){
                 $OrderID := $OrderID;
                 $CustomerID := $CustomerID;
                 $EmployeeID := $EmployeeID;
                 $EmployeeID2 := num2str($1.EmployeeID);
                 $LastName := concat($1.LastName,":",$1.FirstName);
              }
        </attr>
  </Node>
 
  In-line transformation for 2.4 and lower ver.:
  <Node id="JOIN" type="HASH_JOIN" joinKey="EmployeeID;EmployeeType" leftOuterJoin="true">
        <attr name="transform">
            import org.jetel.component.DataRecordTransform;
            import org.jetel.data.*;
 
            public class reformatJoinTest extends DataRecordTransform{
 
                int recNo = 0;
 
                public boolean transform(DataRecord[] source, DataRecord[] target){
 
                    target[0].getField(0).setValue(source[0].getField(0).getValue());
                    target[0].getField(1).setValue(source[0].getField(1).getValue());
                    target[0].getField(2).setValue(source[0].getField(2).getValue());
                    if (source[1]!=null){
                        target[0].getField(3).setValue(source[1].getField(0).getValue());
                        target[0].getField(4).setValue(source[1].getField(1).getValue());
                    }else{
			System.out.println("Slave record not found for " + recNo + "th record.");
                    }
                    recNo++;
                    return true;
                }
            }
        </attr>
  </Node>
 
  In-line transformation since 2.5 ver.:
  <Node id="JOIN" type="HASH_JOIN" joinKey="EmployeeID;EmployeeType" leftOuterJoin="true">
        <attr name="transform">
            import org.jetel.component.DataRecordTransform;
            import org.jetel.data.*;
 
            public class reformatJoinTest extends DataRecordTransform{
 
                int recNo = 0;
 
                public boolean transform(DataRecord[] source, DataRecord[] target){
 
		    if (source[1] == NullRecord.NULL_RECORD) {
			System.out.println("Slave record not found for " + recNo + "th record.");
		    }
                    target[0].getField(0).setValue(source[0].getField(0).getValue());
                    target[0].getField(1).setValue(source[0].getField(1).getValue());
                    target[0].getField(2).setValue(source[0].getField(2).getValue());
                    target[0].getField(3).setValue(source[1].getField(0).getValue());
                    target[0].getField(4).setValue(source[1].getField(1).getValue());
                    recNo++;
                    return true;
                }
            }
        </attr>
  </Node>

This component is deprecated. Use MergeJoin (Ext) instead.

Joins sorted records on input ports. It expects driver stream at port [0] and slave streams at other input ports. Each driver record is joined with corresponding slave records according to join keys specification. The method transform is every composed of driver and corresponding slaves. There are three join modes available: inner, left outer, full outer.

Inner mode processess only driver records for which all associated slaves are available.
Left outer mode furthermore processes driver records with missing slaves.
Full outer mode additionally calls transformation method for slaves without driver.

In case you use outer mode, till 2.4 version be sure your transformation code is able to handle null input records. From 2.5 version it doesn't happen any more, because for lacking record there is used special null record - all getValue methods returns null instead of throwing exception. If you want to realise some action for such record you can compare it with NullRecord.NULL_RECORD (see example below).

Input ports: * 0 - sorted driver record input.

• 1..n - sorted slave record inputs.

Output ports:

• one output port defined/connected.

Xml attributes:

Example:

  <Node id="JOIN" type="MERGE_JOIN" joinKey="CustomerID" transformClass="org.jetel.test.reformatOrders"/>
 
  <Node id="MERGE_JOIN0" 
        joinKey="seqKey"
        slaveOverrideKey="seqKey"
        type="MERGE_JOIN">
        <attr name="transform">
            ${out.0.car} = ${in.0.car};
            ${out.0.seqKey} = ${in.0.seqKey};
            ${out.0.mobilephone} = ${in.0.mobilephone};
            ${out.0.financial_bonus} = ((${in.1.monthly_bonus})*12)+(${in.1.yearly_bonus});
        </attr>
  </Node>
 
  In-line transformation for 2.4 and lower ver.:
  <Node id="JOIN" type="MERGE_JOIN" joinKey="EmployeeID;EmployeeType" leftOuterJoin="true">
        <attr name="transform">
            import org.jetel.component.DataRecordTransform;
            import org.jetel.data.*;
 
            public class reformatJoinTest extends DataRecordTransform{
 
                int recNo = 0;
 
                public boolean transform(DataRecord[] source, DataRecord[] target){
 
                    target[0].getField(0).setValue(source[0].getField(0).getValue());
                    target[0].getField(1).setValue(source[0].getField(1).getValue());
                    target[0].getField(2).setValue(source[0].getField(2).getValue());
                    if (source[1]!=null){
                        target[0].getField(3).setValue(source[1].getField(0).getValue());
                        target[0].getField(4).setValue(source[1].getField(1).getValue());
                    }else{
			System.out.println("Slave record not found for " + recNo + "th record.");
                    }
                    recNo++;
                    return true;
                }
            }
        </attr>
  </Node>
 
  In-line transformation since 2.5 ver.:
  <Node id="JOIN" type="MERGE_JOIN" joinKey="EmployeeID;EmployeeType" leftOuterJoin="true">
        <attr name="transform">
            import org.jetel.component.DataRecordTransform;
            import org.jetel.data.*;
 
            public class reformatJoinTest extends DataRecordTransform{
 
                int recNo = 0;
 
                public boolean transform(DataRecord[] source, DataRecord[] target){
 
		    if (source[1] == NullRecord.NULL_RECORD) {
			System.out.println("Slave record not found for " + recNo + "th record.");
		    }
                    target[0].getField(0).setValue(source[0].getField(0).getValue());
                    target[0].getField(1).setValue(source[0].getField(1).getValue());
                    target[0].getField(2).setValue(source[0].getField(2).getValue());
                    target[0].getField(3).setValue(source[1].getField(0).getValue());
                    target[0].getField(4).setValue(source[1].getField(1).getValue());
                    recNo++;
                    return true;
                }
            }
        </attr>
  </Node>