1.1.1.11 Release 19.1.0.0.0 - August 2019

This section lists the new features added in the OSA 19.1.0.0.0 release.

1.1.1.11.1 Advanced Pipeline

A pipeline defines the pipeline logic and is a sequence of data processing stages. A stage can be one of the following types – Query, Pattern, Rule, Query Group, Custom, and Scoring. A pipeline starts with a stream stage and can have one or more children of any type such as Query, Rule Pattern etc.

Oracle Stream analytics 19.1 introduces advanced pipeline features like splitting a pipeline into multiple branches at any stage as per your application logic. You can end each branch with one or more targets. It provides enhanced editing capabilities like editing intermediate stages and the changes due to that are propagated to downstream stages. You can now edit the sources even if those are already being used in any pipelines. With a pipeline, you can switch the streams in the source and will be notified of the corrective actions you will need to accommodate the change in source. You can now also use output of an existing stage as one of the source for another stage in the pipeline.

1.1.1.11.2 Supported Window Types

Window support in Oracle Stream Analytics in 19.1 is enhanced by the addition of following new types:

  • Current Year
  • Current Month
  • Current Day
  • Current Hour
  • Current Period
  • Constant Value
  • Variable Range
  • Partition Window Types

1.1.1.11.3 Import/Export

The export and import feature lets you migrate your pipeline and its contents between Oracle Stream Analytics systems (such as development and production) in a matter of few clicks.

Oracle Stream Analytics 19.1 now supports the operation on all types of artifacts including Visualizations, Cubes, Dashboards, Scoring Stage and Custom Stage. When you import and export, any custom jar that you use in the pipeline is also taken care during the operation. It allows you to review the export bundle, edit names and description of artifacts and manage the tags during the export. During import, it allows you to inspect the import bundle, select items to import and manage tags at the time of import.

1.1.1.11.4 LDAP Integration

The Lightweight Directory Access Protocol (LDAP) is an open source application accepted across various industries. This application protocol is used for obtaining and maintaining distributed directory information services over a network using an Internet Protocol (IP).

Oracle Stream Analytics makes use of the LDAP support for Jetty OSA. With this feature, you can use the directory information services for authentication/user management. The authentication/user management can be through either internal LDAP or external LDAP.

1.1.1.11.5 Coherence POJO

Oracle Stream Analytics 19.1 enables the support for referencing coherence cache where cache value is stored as POJO. The current support involves cache value as a Map<String, Object>. Oracle Stream Analytics application can enrich stream data with POJO data.

1.1.1.11.6 IN Operator Support in Filters

The IN Operator is supported in filters at various stages of the application in Oracle Stream Analytics. This option is available as an operator in the drop-list where you apply any filter.

1.1.1.11.7 Multihost Coherence

Oracle Stream Analytics now supports configuring multiple hosts while creating the coherence connection. In the coherence connection application, you can now specify multiple server URLs.

Oracle Stream Analytics supports POJO and Map for Coherence cache.

1.1.1.11.8 Webtier HA

Oracle Stream Analytics 19.1 supports High Availability for its Webtier. Based on the expected load on the Oracle Stream Analytics 19.1 Webtier, you can now configure multiple hosts running the webtier and use NGNIX as a load balancer to configure the High Availability of the OSA Webtier.

1.1.1.11.9 Google Tile Layer

Oracle Stream Analytics has added the support for Google tile layer which displays Google maps in Spatial patterns and visualizations. You can configure the Google tile layer under User Preferences of the Map tab.

Note:

In order to use Google maps tile layer, the usage of the maps must meet the terms of service defined by Google (http://code.google.com/apis/maps/faq.html#tos).