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.1
Troubleshooting
ASN1Parse Operator

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
Learn about different Teracloud Streams tools and features to write, compile, run, and test streams applications.
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.
- Metrics
  Teracloud® Streams provides metrics to help evaluate the health of Teracloud Streams services, to aid in diagnosing performance issues, and to analyze throughput of requests. You can use the streamtool checkinstancemetrics, streamtool checkdomainmetrics, streamtool getdomainmetrics, and streamtool checkresourcemetrics commands to view the metrics data.
- 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.
- SPL Compiler
  The SPL compiler is an incremental compiler that generates artifacts needed to run your stream application. These artifacts include, for example, C++ code for several entities in your SPL program and an application bundle file.
- 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.

ASN1Parse Operator

To isolate and resolve problems with the ASN1Parse operator, you can use the troubleshooting and support information in this section.

Circular ASN.1 definitions are partially supported: ASN.1 supports circular definitions, but the ASN1Parse operator only partially supports them.

ASN.1 default value handling is partially supported: ASN.1 supports the definition of default values within the ASN.1 structure definition document.

Multi-dimensional fields are not supported: Consecutive SEQUENCE OF constructs are not supported.

Inner container definitions are not supported: ASN.1 supports the definition of containers (SEQUENCE, SET or CHOICE) in containers, either with inner or separate definitions for each container.

Constraints verification is partially supported: ASN.1 supports constraints that can restrict possible values for types. Such constraints can be a restricted alphabet for a string type, for example for PrintableString, or user-defined constraints that are written to the ASN.1 structure definition file, for example a size limitation for an OCTET STRING.

Your ASN.1 root element has the wrong container type: The ASN1Parse operator requires that the pdu parameter references a SEQUENCE, SET, or CHOICE ASN.1 element. It does not allow you to select a defined ASN.1 element, as shown in the following example:

The build generates errors: If the C++ class files that are generated from the SPL source code are not up-to-date, build errors can occur.

ASN1Parse is healthy but stops to emit tuples: This can occur if the input data contains padding bytes.

ASN1Parse emits less tuples than expected: This can happen if input data does not conform to the grammar.

ASN1Parse emits empty tuples: This can happen if output schema does not conform to the trigger.