Page Comparison

 Custom fields with data stream

Data publishers generally allow you to send data to a predefined set of data fields, to the BAM/CEP server only specified in the stream definitions. This is a set of fixed data fields you send through a data bridge. You can also send custom key-value pairs with data events.

...

1. When the key starts with meta:       The data field is considered as a metadatacustom field. It is sent with metadata and saved in Cassandra with key prefix meta_.
2. When the key starts with correlation: The data field is considered as a correlation data custom field. It is sent with correlation data and saved in Cassandra with key prefix correlation_.
3. When the key starts with payload or any other string : The data field is considered as a payload data custom field. It is sent with payload data and saved in Cassandra with key prefix payload_.

...

In order to publish data to BAM through a custom data agent you need to have below dependencies.

Either you can add below jars to your class path 

• commons-logging-1.1.1.jar
• commons-pool-1.5.0.wso2v1.jar
• commons-pool-1.5.jar
• gson-2.1.jar
• httpclient-4.1.1-wso2v1.jar
• json-2.0.0.wso2v1.jar
• libthrift-0.7.wso2v1.jar
• org.apache.log4j-1.2.13.v200706111418.jar
• org.eclipse.osgi-3.8.1.v20120830-144521.jar
• org.eclipse.osgi.services-3.3.100.v20120522-1822.jar
• org.wso2.carbon.bootstrap-4.2.0.jar
• org.wso2.carbon.databridge.agent.thrift_4.2.0.jar
• org.wso2.carbon.databridge.commons_4.2.0.jar
• org.wso2.carbon.databridge.commons.thrift_4.2.0.jar
• org.wso2.carbon.logging-4.2.0.jar
• slf4j-1.5.10.wso2v1.jar
• wrapper-3.2.3.jar

<repositories>
    <repository>
        <id>org.wso2.carbon</id>
        <url>http://dist.wso2.org/maven2/</url>
    </repository>
</repositories>

<dependency>
	<groupId>org.wso2.carbon</groupId> 
	<artifactId>org.wso2.carbon.databridge.agent.thrift</artifactId> 
	<version>4.2.0</version>
</dependency> 
<dependency>
	<groupId>org.wso2.carbon</groupId> 
	<artifactId>org.wso2.carbon.databridge.commons</artifactId> 
	<version>4.2.0</version> 
</dependency>

...

After publishing the call center data, you can query it with variable keys using Hive scripts.

...

This is the result of the query: