IBM InfoSphere Streams Version 4.1.0
Namespaces: SPL standard and specialized toolkits
SPL standard and specialized toolkits > Namespaces
Namespaces
- com.ibm.streams.bigdata.dataexplorer
- com.ibm.streams.cep
- com.ibm.streams.cybersecurity.analytics
- com.ibm.streams.cybersecurity.extractors
- com.ibm.streams.cybersecurity.tagging
- com.ibm.streams.cybersecurity.types
- com.ibm.streams.db
- Testing ODBC connections: You can use the odbchelper program in the Database Toolkit to help you find setup and configuration issues in ODBC connections.
- com.ibm.streams.db.db2
- Testing connections to DB2® databases: You can use the db2helper program in the Database Toolkit to test the connection to a DB2 database and determine the number of partitions in the database.
- com.ibm.streams.db.netezza
- com.ibm.streams.financial
- The finance-specific SPL types and schemas are in the com.ibm.streams.financial SPL namespace of the Financial Services Toolkit. OptionType is a simple enumeration with two values: put and call.
- com.ibm.streams.financial.adapters.fix
- The Financial Services Toolkit provides a collection of four operators to support the FIX protocol.
- com.ibm.streams.financial.analytics.equity
- com.ibm.streams.financial.analytics.equity.strategy
- com.ibm.streams.financial.analytics.option
- The Financial Services Toolkit contains two operators that can be used for pricing of equity options.
- com.ibm.streams.financial.utility
- com.ibm.streams.financial.utility.Greeks
- com.ibm.streams.financial.utility.trade
- com.ibm.streams.geospatial
- com.ibm.streams.geospatial.conversions
- com.ibm.streams.geospatial.ext
- com.ibm.streams.geospatial.st
- com.ibm.streams.geospatial.twodimension.geometry
- NOTE: The com.ibm.streams.geospatial.twodimension.geometry namespace and all types and functions defined therein are deprecated.
- com.ibm.streams.mining.scoring
- The Mining Toolkit has four toolkit operators.
- com.ibm.streams.rproject
- com.ibm.streams.rules.odm
- com.ibm.streams.teda.encoder.binary
- com.ibm.streams.teda.file
- The C++ native functions under this namespace enable you to create directories and to rename files and directories.
- com.ibm.streams.teda.parser.binary
- Because most telecommunications network data is available only in binary data formats, the Telecommunications Event Data Analytics toolkit includes parser operators that can parse binary-encoded data.
- com.ibm.streams.teda.parser.text
- com.ibm.streams.teda.utility
- Under this namespace you can find some utility C++ primitive operators and C++ native functions that are also useful outside of telecommunications applications.
- com.ibm.streams.text.analytics
- com.ibm.streams.timeseries
- com.ibm.streams.timeseries.analysis
- com.ibm.streams.timeseries.distance
- com.ibm.streams.timeseries.generators
- com.ibm.streams.timeseries.modeling
- com.ibm.streams.timeseries.preprocessing
- com.ibm.streamsx.hbase
- com.ibm.streamsx.hdfs
- com.ibm.streamsx.inet
- com.ibm.streamsx.inet.http
- com.ibm.streamsx.lock.distributed
- com.ibm.streamsx.messaging.jms
- Conversions between JMS messages and tuples in IBM® InfoSphere® StreamsWhen you send data to or receive data from WebSphere® MQ or an Apache Active MQ queue or topic by using JMSSink or JMSSource operators, IBM InfoSphere Streams must convert tuples to JMS messages, or vice-versa.
- com.ibm.streamsx.messaging.kafka
- com.ibm.streamsx.messaging.mqtt
- Operator control input port: Some of the operators in the Messaging Toolkit provide the capability to specify an optional control input port.
- com.ibm.streamsx.messaging.xms
- Conversions between XMS messages and tuples in IBM InfoSphere StreamsWhen you send data to or receive messages from a WebSphere MQ queue or topic by using XMSSink or XMSSource operators, IBM InfoSphere Streams must convert the XMS message to a tuple, or vice versa.
- com.ibm.streamsx.sparkmllib.classification
- com.ibm.streamsx.sparkmllib.clustering
- com.ibm.streamsx.sparkmllib.collaborativefiltering
- com.ibm.streamsx.sparkmllib.regression
- com.ibm.streamsx.sparkmllib.tree
- com.ibm.streamsx.store.distributed
- com.ibm.streamsx.topology
- com.ibm.streamsx.topology.topic
- Topic based publish-subscribe model for streams.
- spl
- The SPL standard toolkit defines several types in the composite operator spl::Sys.
- spl.XML
- Character encoding of XML: If the input is contained in an ustring value, then it is already in Unicode and internal encoding is ignored if it is present.
- spl.adapter
- Schema checking for TCP operators using the confirmWireFormat parameter: Use the confirmWireFormat parameter on TCPSource and TCPSink operators to confirm that the transmitted data is compatible.
- spl.collection
- This namespace contains components for handling collections.
- spl.compat
- SPADE operators: The Stream Processing Application Declarative Engine (SPADE) language was introduced with the original release of IBM InfoSphere Streams.
- spl.control
- This namespace contains components for creating and using a job control plane that can be used to communicate control information between operators within a job.
- spl.file
- This namespace contains components for handling files.
- spl.math
- This namespace contains components for performing mathematical computations.
- spl.relational
- This namespace contains components that can transform streams using relational predicates.
- spl.string
- This namespace contains components for handling strings.
- spl.time
- This namespace contains components for handling times and timestamps.
- spl.utility
- This namespace contains components of general utility that include customizable operators, and functions for obtaining configuration information, logging, managing consistent regions and using custom metrics.