TIBCO® Spotfire Data Streams 10.4.4 adds the following updates and new features:
- New OPC UA Adapter Suite Added
The TIBCO StreamBase® Adapter for OPC UA (Open Platform Communications Unified Architecture) allows StreamBase to interact with data from an OPC UA infrastructure. The adapters in this set are only available for Microsoft Windows platforms and include:
The OPC UA Control adapter, which is used to control the connection with the OPC UA server (connection, disconnection, server status, and so on).
The OPC UA Reader adapter, which is used to retrieve values from OPC UA Variable nodes.
The OPC UA Writer adapter, which is used to write values to OPC UA Variable nodes.
The OPC UA Subscriber adapter, which is used to subscribe to Variable nodes and get continuous updates when the nodes' values change.
The OPC UA Browser adapter, which is used to traverse the OPC UA server's node hierarchy and retrieve metadata for these nodes.
See this sample page for a demonstration of these adapters.
- New rebalance availabilityzone Command Option Added
The epadmin rebalance availabilityzone command now includes a new option,
wait. When set to true, the command only returns when availability zone rebalancing is completed.
- ActiveSpaces Operators New Features
The ActiveSpaces operators now support configuration for backup TIBCO FTL realm servers. See this page for operator configuration details.
The operators now provide a
datagrid-idconfiguration element that supports the multiple data grid feature of ActiveSpaces 4.
- Oracle CDC LogMiner Adapters Now Work With non-CDB Databases
- Oracle JDK Version Updated
The Oracle JDK version bundled with StreamBase and Live Datamart is now JDK 1.8.0_u212.
- ep-maven Plugin Now Supports Running Browse Services
The ep-maven plugin now supports running browse services in the administer-nodes goal. This change allows calling browse services from system test cases that use the Maven plugin.
- Edit Module Import Dialog Improved
Edit Module Import dialog improvements include a larger default dialog size, and the option is now the default. The Importing Resources from One Module to Another page was updated for to provide a StreamBase 10 focus.
This release includes the following changes in functionality:
- FTL Adapter Library Support Updated
The TIBCO FTL adapters now support FTL library 5.0 and higher as well as 6.x.
- Artifact Command Support For Multiple Registrations Now Enhanced
The epadmin register artifact command was updated to support deploying a new version of an artifact — even when there are multiple registrations for the artifact type. The artifact name is now used to choose the artifact registration being updated by the command.
- Kafka Adapter Now Changed for Null Offset and Null Time Configuration
The Kafka Consumer Adapter was changed so that null offset and null time now mean "do not perform a seek operation" on startup. Instead, the adapter simply connects and allows the default operation occur. See this page for adapter configuration details.
- Documentation Updates
This release includes the following updates and corrections to the documentation:
- Time Zone Information Updated
All expression language descriptions in the Simple Functions: Timestamp Overview section of the StreamBase Expression Language Functions page were reviewed and updated to modernize the discussion of time zone settings, using the newest canonical zone string information shown in references such as Wikipedia's List of tz Database Time Zones. The Specifying Time Zones section of the Data Types page was similarly updated.
- Function Data Type Redocumented
Documentation for the
functiondata type was consolidated into a single new page in the Authoring Guide, then reworked and expanded. Sections about
functionin the Data Types and Expression Language Features pages were reduced to introductory material that point to the new page. The Function Data Type sample was also reworked to support the new documentation.
- System Control Stream's CLUSTER Subsystem Documented
Documentation for the
systemcontainer was consolidated into a single page, then reworked and expanded, adding the CLUSTER subsystem of the
system.controlstream. The Container Overview page was reworked for StreamBase 10.
- Custom Function Documentation Reworked
For the previous 10.4.3 release, documentation in the StreamBaseEngine root object for its streamBase>pluginFunctions object was updated and clarified. For this 10.4.4 release, that documentation was corrected and updated again, and now includes a table of differences to help you port your configuration settings from release 10.4.2 or earlier.
- Iterate Operator Page Rewritten
The Authoring Guide's page for the Iterate Operator was substantially rewritten for clarity, this time providing examples.
StreamBase 10.4.4 includes the following deprecations.
- Spark Model Operator Deprecated
The TIBCO StreamBase® Operator for Spark/MLlib Model Evaluator is now deprecated and is expected to be removed in a future release.
- pluginFunctions HOCON object
The pluginFunctions object in the StreamBaseEngine root object is now deprecated. An upcoming release is expected to provide a new root object in the sbengine HOCON type in order to register custom Java functions and function aliases.
This section describes known limitations as of the current release of the TIBCO StreamBase® component of TIBCO® Spotfire Data Streams. Each item includes a tracking number, description, and workarounds when possible.
|CQS‑4679||All identical adapters and operators in an application that use the Operator getlogger() method share the same log level configuration.|
If you have multiple identical StreamBase or LiveView operator or adapter instances based on a given Java class in a StreamBase fragment, they all share a Logger object, and the log level of the last instance to be initialized is used.
|Workaround||Parameterize the log level of all the adapters of a specific class and expose that parameter through the fragment's
|SB‑46022||Nested list fields are not supported in replica delta streams.|
Nested list fields are currently not supported in replica delta streams. They are instead skipped with a warning log message.
|SB‑46208||Multiple aliases to the same method not allowed until release 10.4.3.|
The HOCON syntax for defining aliases for custom Java methods did not allow a way to define more than one alias for the same method.
|Workaround||Upgrade to release 10.4.3 or later and use the methodName property in your HOCON alias definitions.|
|SB‑45974||Workspace error after importing a project with dependencies on JARs not present.|
You may encounter saved Studio projects that have dependencies on JAR files that cannot be shipped with that saved project, such as JARs with licenses independent of StreamBase. In some cases, such projects cannot be resolved, even with> . This can happen with StreamBase examples that use TIBCO EMS, because the JAR files that implement EMS are licensed separately from StreamBase.
|Workaround||Before trying to run such projects, obtain the referenced JAR files from their vendor and Maven-install them to your local Maven repository (or to a site-specific network repository), as described in Using External JAR Files.|
|SB‑45757||Typecheck failure: "Could not find" resource file.|
The EventFlow Editor can get into a state where a resource file, such as a CSV file used to preload a Query Table, is not found during typechecking, resulting in a typecheck failure with no corresponding entry in the Problems view.
|Workaround||Re-run the EventFlow Editor's typechecker with with Ctrl+T (Windows) or Cmd+T (Mac). Note that the menu command Refresh Project Typecheck Environment invoked with Ctrl+F5 (Windows) or Cmd+R (Mac) does not resolve this condition; you must run the Editor's typechecker independently.|
|SB‑45183||ResourceUnavailableException after stopping two nodes and restarting one node.|
|Description||When stopping more than one node in a cluster, on restart of just one of the stopped nodes a
|Workaround||Restart all the stopped nodes concurrently or reinstall the node before restarting.|
|SB‑45182||Default availability zone may not be created correctly when cluster stopped and started.|
|Description||If a node in a cluster is stopped and then restarted, the default availability zone may not be created correctly.|
|Workaround||Remove the node and reinstall before starting.|
|SB‑45146||Welcome launch bar shows a large red square.|
|Description||The Welcome launch bar that appears in Studio's bottom right status bar is missing an icon, which the system replaces with a red square. On Windows, this red square can be confused with the Console view's red Terminate button.|
|SB‑44167||iPhone connected to Mac can cause node launch failures.|
|Description||Conditions: an iPhone is connected to a Mac with a USB-to-Lightning cable (including USB-C-to-Lightning cables) while Personal Hotspot is NOT enabled on the iPhone. Under these conditions, StreamBase Runtime nodes can fail to start, possibly emitting an error message similar to "can not see the local file system. Deploy to remote nodes is not supported."|
|Workaround||Unplug the iPhone, or enable Personal Hotspot (whether or not you actually use Personal Hotspot).|
|SB‑42478||Cluster Monitor fails to start in the same cluster as monitored.|
|Description||Attempting to start the Cluster Monitor in the same cluster as other applications can fail.|
|Workaround||Run the Cluster Monitor feature in a separate cluster from the one containing the applications being monitored.|
|SB‑42410||Duplicate engine log files.|
|Description||Duplicate engine log files exist in both the node directory's top level and in its
|Workaround||None. The engine log files in the node directory's top level can be ignored. The same information is available in the engine
log files found in the
|SB‑42324, SB‑30773, SB‑30846||Inconsistent containerName behavior.|
|Description||If you define a StreamBase container name with the
|SB‑42093||Reloading the entire node configuration when attempting to configure the cluster monitor fails.|
|Description||Attempting to reload a cluster monitor configuration embedded in a node deploy configuration file using the epadmin load configuration command quietly does nothing.|
|Workaround||Create a separate configuration file with just the cluster monitor configuration and load and activate that configuration.|
|SB‑41896||Studio Support Wizard screen capture can fail on Mac.|
|Description||The StreamBase Support Wizard screenshot feature preview may not display properly under certain multi-monitor and/or Retina display hardware conditions.|
|Workaround||Use the Support Wizard to guide you to continue; the Support zip file will still contain the screenshot that you can verify in the archive prior to sending to TIBCO. For more information on the Support Wizard, see StreamBase Support Wizard for Troubleshooting.|
|SB‑41099||Calling Help via management API throws null pointer exception|
|Workaround||None. This issue is expected to be resolved in a future release.|
|SB‑35326||Shutting down at debugger breakpoint causes engine to fail with an error.|
|Description||Stopping a JVM with a breakpoint set in the debugger can cause the JVM to exit with an error that requires the node to be removed and reinstalled.|
|Workaround||Ensure that no breakpoints are set in a debugger when shutting down a JVM.|
|Description||When deploying fragments, a misleading fatal error message may be returned when terminating the fragment or the node on which
it is deployed. For example:
MESSAGE: dtm : FATAL(RQ:A.dstest): Invalid response: <ready/>
|Workaround||This message can be safely ignored.|
|SB‑31125||Cluster-wide queries fail for disk-based Query Tables|
|Description||Cluster-wide queries do not work on disk-based Query Tables.|
|SB‑30948||Trouble using the TERR operators on macOS.|
|Description||On macOS, EventFlow modules that use the TERR operators with TERR versions before 4.4 fail to start even when using the Use Embedded TERR check box. This includes the TERR operator samples shipped with StreamBase.|
|Workaround||If you can, update to TERR 4.4 or later, which is included with StreamBase 10.2.1 and later. If you must use a TERR version before 4.4, there are extra configuration steps on macOS, compared to Windows and Linux. These steps are detailed in the Operating System Configuration for TERR sections of the pages that describe the TERR Operator and the TERR Predict Operator.|
|SB‑30898||On Windows only, virtual network adapters slow fragment startup with StreamBase before 10.3.0.|
|Description||If you have Oracle VM VirtualBox® or Microsoft Hyper-V installed, and one or more of your virtual machines has its virtual network adapter activated, this slows down the launch of EventFlow and LiveView fragments into a StreamBase Runtime node by several minutes.|
|Workaround||Upgrade to StreamBase 10.3.0 or later, where this issue is corrected. If you must use an earlier release, temporarily disable the network adapter feature of your VirtualBox VMs as described in Windows and Virtual Network Interfaces.|
|SB‑30270||Failure to start Studio or Manager by double-clicking on macOS Sierra or High Sierra|
|Description||MacOS releases 10.12 Sierra and 10.13 High Sierra have a security model that is stricter than previous releases. As part of
their security, these releases automatically block unsigned, downloaded application bundles with
|Workaround||See the list of suggested workarounds in Starting StreamBase Studio on macOS Sierra.|
|SB‑29050||Error when debug stepping into or stepping over a Decision Table operator.|
|Description||When using EventFlow debugging, stepping into or over a Decision Table operator is not supported.|
|Workaround||Set your breakpoints upstream or downstream. Also, consider using the features of the Decision Table Analyzer to get a debug-like view of how the operator responds to different input tuples.|
|SB‑28856||Deleting decision table rows does not re-number rule IDs.|
|Description||When using the Decision Table editor to delete and then add a new decision table rule, the rule ID does not renumber. For example, by deleting row 5 and adding a new row, the rule ID numbering is now 1...4, 6.|
|SB‑28669||Error message: Grows beyond 64KB.|
|Description||In rare cases, compiling small StreamBase applications can produce an error message containing the words
|Workaround||Contact TIBCO StreamBase Technical Support for a workaround for this issue.|
|SB‑28598||Multi-container StreamBase applications cannot use the same ActiveSpaces metaspace.|
|Description||StreamBase applications deployed with multiple containers receive
|SB‑28452||Delta stream arc limitations in the EventFlow Debugger.|
|Description||If a delta stream arc is a direct connection between a Query Table and an Output Stream, and if that arc has a Debugger breakpoint, the breakpoint is not hit at during debugging with the EventFlow Debugger. Similarly, while debugging, stepping over to try to reach that arc does not suspend on that arc.|
|Workaround||Insert a no-op Map operator between the Query Table and the Output Stream. Then a breakpoint on the arc between the Query Table and the Map does work, and stepping over reaches that arc as well.|
|SB‑26629||RPM installation method issues on RHEL 7|
|Description||StreamBase and LiveView are supported on Red Hat Enterprise Linux version 7.x. The archive installer is the recommended installation
method. If you use the RPM installation method, RHEL 7 issues several warning messages during installation that complain about
file removal failures, and issues an overall warning that RHEL 7 "may not be compatible with this version of StreamBase."
Despite these warnings, the installation does succeed. The only consequence is that
|Workaround||Remove StreamBase directories manually to uninstall an RPM installation on RHEL 7. Otherwise, all StreamBase and LiveView processes run as expected on RHEL 7.|
|Description||In compiling the updating expression for a dynamic variable where the expression references a named schema, if a field in
the tuple presented by the updating stream also has the same name as the named schema used in the expression, the field is
instead evaluated as a function. This raises the error
|Workaround||The required migration step is to rename either the field or the named schema to eliminate the ambiguity.|
|SB‑26237||Constant definitions used as component properties are not used at runtime.|
|Description||StreamBase Studio properly typechecks defined constants when used in operator properties, but at runtime substitutes their names instead of their values.|
|Workaround||Do not use defined constants when specifying operator properties.|
|SB‑26017||Asynchronous timeouts for Gather operators in parallel applications can be inaccurate|
|Description||High availability applications that include Gather operators may incorrectly compute timeout intervals because the operator relies on now() instead of calling out to the parallel scheduling service.|
|SB‑22297||Commented-out error input streams consume error tuples.|
|Description||An error input stream, despite being disabled with the EventFlow comment-out feature, still catches errors thrown, but consumes any incoming errors and fails to pass them on.|
|Workaround||To temporarily disable error streams, copy them to a placeholder module and remove them from the active module.|
|SB‑21843||In the TableAccessor API, ClassCastException is thrown if not using a Tuple from TableAccessor#createRow.|
|Description||If methods in the
|SB‑20449||Display issues with years before 2 AD.|
|Description||The timestamp data type can hold timestamp values in the range -(2^62) to (2^62)-1, and can successfully display any future date in the next 146 million years and any past date to around year 2 AD. However, the year value for dates earlier than 2 AD may not display correctly.|
|SB‑18294||Union operator: sub-field order of tuple fields must match with strict options.|
|Description||When using the Union operator with its Strict union or Declared schema options, the order of sub-fields of tuple fields must match exactly. This is in contrast with the default Loose union option, where strict sub-field ordering is no longer required.|
|SB‑16594||Extract as Module feature copies items instead of importing them.|
|Description||The Extract as Module feature makes a copy of the source module's definitions and named schemas, and places the copies in the newly created module. Best practice would be to import those features from the source module to the new module, and to copy all imports from the source to new modules.|
|Workaround||After using Extract as Module, manually convert the copied definitions and named schemas to imports.|
|SB‑14133||On Linux, sb-config --cxx returns a setting for G++ newer than 4.5.|
|Description||On Linux, in StreamBase samples that build C++ code, some of the example Makefiles show sb-config --cxx as the correct usage to determine the G++ compiler to use. On newer Linux distributions, this command returns the distribution's default G++ compiler, which may not be supported for building StreamBase client code, and sb-config does not honor the CC and CXX environment variables.|
|Workaround||On such systems, install GCC and G++ 4.5, and edit the Makefiles to specify
|SB‑13398||Filter operators with very large predicate settings may result in a runtime EvalException error.|
|Description||Filter operators with several output ports and complex expressions to evaluate for each port may result in a
|Workaround||Add another Filter operator and split the predicate settings between the two Filter operators.|
|SB‑13113||Application output view does not display UTF-8 characters.|
|Description||Both StreamBase Server and StreamBase Studio are fully capable of processing and displaying Unicode character sets, but neither is set to do so by default.|
|Workaround||Follow the instructions in Unicode Support to configure StreamBase Server, Studio, and any StreamBase client applications to process the UTF-8 character set.|
|SB‑10792||The Query operator converts a JDBC data type differently when using explicit schemas than when using database data types.|
|Description||When explicit schemas are used, the Query operator does not use database metadata to determine the mapping between JDBC data
types and StreamBase data types. The JDBC data type
|SB‑10486||Hierarchical data restrictions.|
|Description||Patterns by value do not support using the tuple data type for their on-value portion. Similarly, tuple subfields cannot be used as the index or primary key of a Query Table.|
|Workaround||Design schemas so that the intended sort field or key is a top-level numeric or timestamp field, as described in StreamBase Pattern Matching Language.|
|SB‑10363||No StreamBase data type corresponding to Sybase timestamp.|
|Description||When used with Sybase data sources, both EvenfFlow and StreamSQL fail to convert timestamps, resulting in typecheck errors.
This is because the Sybase
|Workaround||In EventFlow or StreamSQL code that will be used for Sybase data sources, use the Sybase
|SB‑6862||Not all databases have native blob support.|
|Description||For example, Microsoft SQL Server and Sybase do not have blob support. For these databases, you can write blobs into varbinary and possibly other types. But when blobs are read from a select statement, they are returned as strings, not blobs.|
|Workaround||Add a Map operator and convert the string to a blob.|
|SB‑5882||Tuple dimensions do not reset counter when another dimension closes a window early.|
|Description||A tuple-based dimension that closes due to other dimensions (for example, after another dimension times out) does not reset its counter. When this happens, the next window will close based on the total number of tuples received, resulting in a partially full dimension.|
|SB‑4559||Join timeout is not asynchronous.|
|Description||Join timeout in the Join operator is not asynchronous. That is, the Join operator does not remove a tuple from its buffer until the timeout has passed and another tuple arrives on the same input stream. Tuples received on one input stream do not affect the buffer of the other input stream.|
This section provides a list of errors corrected in release 10.4.4 of the TIBCO StreamBase® component of TIBCO® Spotfire Data Streams.
|Fixed in 10.4.4|
|TIBCO StreamBase® 10.4.4 incorporates all fixes resolved in the release 7.7 series through 7.7.7.|
|SB‑46838||The Oracle CDC LogMiner adapters longer generate an NPE when a date column is assigned a null value.|
|SB‑46806, SB‑46803||The Artifact Distribution Service (ADS) was incorrectly registering artifacts more than once. The epadmin register artifact command was updated to no longer invoke the operator's artifact notifier if the operator is already using the artifact being registered.|
|SB‑46776||Restarting a node failed when the Distributed Router operator was used in modules with partition-based routing. This was resolved.|
|SB‑46766||SBHPFIX dictionaries were inadvertently omitted from Windows and Linux versions of StreamBase in a previous release. This was fixed.|
|SB‑46656||The strptime() expression language function was not correctly handling invalid time zone strings. This was fixed.|
|SB‑46648||OSI PI adapters now correctly mask the password field and also decipher encoded passwords.|
|SB‑46646||A problem with timestamps for start-of-day log messages was resolved.|
|SB‑46632||Previously, Studio's typecheck environment would not update when HOCON configuration files were moved. This was resolved.|
|SB‑46539||In rare situations, rebalancing of partitions would fail to complete. This was resolved.|
|SB‑46519, CQS‑4810||StreamBase expressions with arbitrary parenthetical nodes are correctly parsed and compiled. However, in some LiveQL query expressions, parts of the query are returned to their string form for additional processing. In some cases, the string form of the expression would be properly formed but have incorrect parentheses which could deliver unexpected results. This was corrected.|
|SB‑46471||The Distributed Router adapter was fixed to correctly handle capture fields.|
|SB‑46419||In some scenarios, a partitioned query table using a named schema would would fail typecheck. This was fixed.|
|SB‑46103||A PersistenceAdapter error would occur at startup when a Query Table in a submodule is referenced by a top-level module. This was resolved in Release 10.4.3.|
|SB‑45789||Previously, when replacing an Artifact Distribution Service (ADS) configuration, no audit of the new configuration version would occur. Now, it does.|