...
The name of the Cassandra column family is "bam_notification_messages", inside the Cassandra data source with the name "WSO2BAM_UTIL_DATASOURCE". For each of the row inserted for "bam_notification_messages" column family, it should contain a column with the name "streamId", which identifies the target stream id (i.e. "stream_name:version") of the stream this record should be written to. The columns other than with the name "streamId" basically is considered payload properties of the target stream, where the column name is the property name and the column value is the property value.
The schedule task used to poll the notifications column family will send the data to the mentioned streams, where those stream can contain a CEP flow, which can define a notification target for the messages to be delivered.
Below contains a sample Hive script snippet, which demonstrates the Hive based notifications.
...
The above snippet can be used with the HTTPD log analyzing sample Hive script.
The Hive script based notifications functionality can be switched off in a specific BAM node by setting the Java system property "disable.notification.task" (i.e. sh wso2server.sh -Ddisable.notification.task).
| Info | ||
|---|---|---|
| ||
Hive Script based Notifications are only support in the default (super) tenant for the moment |