Home
Reference
Find details on the SPL language, toolkits, APIs, commands, and more.
Toolkits
A toolkit is a set of SPL artifacts, which are organized into a package. Toolkits make SPL or native functions and primitive or composite operators reusable across different applications.
Toolkits
Toolkit com.teracloud.streams.teda 4.0.0
Developing applications
Configuring Solutions
Configuring ITE Applications
Data ingestion
Choosing a parser

Welcome
Learn about the core capabilities of Teracloud® Streams, its architecture, and key concepts.
Installing
Use this information to install, upgrade, and uninstall the Teracloud® Streams product.
Configuring
Create a basic or an enterprise domain which is a single point for configuring and managing common resources, security, and instances.
Administering
Administer the product by using the Teracloud® Streams graphical user interface, APIs, or the streamtool command-line interface.
Developing
Develop stream applications with the Streams Processing Language (SPL), Java, and Python.
Troubleshooting
Resolve problems with Teracloud® Streams using the troubleshooting tools provided with the product as well as the resources offered by Teracloud Support.
Reference
Find details on the SPL language, toolkits, APIs, commands, and more.
- APIs
  Application programming interfaces (APIs) provide functions that simplify applications development.
- Job configuration overlays
  You can specify or change configuration parameters when you use the submitjob or updateoperators operations. The settings control submission constraints, host constraints and locations, and operator status. Parameters are captured and updated in the configuration JSON file. When you change the values in the job configuration overlay file, the changes override any previously set values.
- Commands
  Teracloud® Streams provides a number of commands you use to perform tasks.
- Operator model
  An operator model is an XML document that describes the basic properties of a primitive operator.
- Streams Processing Language (SPL)
  Streams Processing Language (SPL) is a distributed data flow composition language that is used in Teracloud® Streams. SPL has primitive types, program structures, and definitions that are tailored for streaming data.
- Toolkits
  A toolkit is a set of SPL artifacts, which are organized into a package. Toolkits make SPL or native functions and primitive or composite operators reusable across different applications.
  - Specialized toolkit requirements and restrictions
    Several of the specialized toolkits require RPMs that are not required by the Teracloud® Streams product. There are also toolkit restrictions on some platforms.
  - Toolkits
- SPLDOC markup
  You can use SPLDOC markup in the descriptions associated with the SPL artifacts in a toolkit. The spl-make-doc command generates HTML documentation from the marked up artifacts.
Glossary
Use this glossary to find terms and definitions for Teracloud® Streams.

Choosing a parser

To read the data from the input files, you need to configure a parser. When one parser reads all input files, this configuration is done fairly easy.

About this task

Configure a parser component to read the input file contents.

Procedure

In the file <PathToYourApplication>/config/config.cfg, find the ite.ingest.customFileTypeValidator parameter description
When you do not need to route different file types to different parsers, you make sure that the type validator is turned off as follows: ite.ingest.customFileTypeValidator=off
In the file <PathToYourApplication>/config/config.cfg, find the ite.ingest.reader.parserList parameter description
Assign the parameter a file type identifier that is combined with a parser class name, for example: ite.ingest.reader.parserList=*|FileReaderCustom

The values that are used for the parameters are in fact their default values. So to achieve the same result as in the description it would be sufficient to ensure that these parameters are not actively used in your configuration file. When the wizard creates the ITE project for you, it provides a FileReaderCustom implementation, too. You need to customize the reader, first by selecting a parser to derive from your implementation. Then, by setting the parser’s parameters according to your use case.