JavaScriptNode.jsNode.jsPhoneGapReactReduxTitaniumVueWebStream Filtering Tutorial for Node.js V4

Stream filtering allows a subscriber to apply a filter to only receive messages that satisfy the conditions of the filter. The message filter is set by the subscribing client(s) but it's applied on the server side thus preventing unwanted messages (those that don't meet the conditions of the filter) from reaching the subscriber.

Stream filters are implemented with two components: meta dictionary on publish and filter expression on subscribe.

 

Filters are applied to all channels that the client is subscribed to. When messages are encrypted (using crypto key when initializing PubNub), the meta dictionary is plain text, so that the PubNub Network can properly apply the filters as required. It is important to only include information that is not confidential or otherwise requiring encryption.

To use stream filtering, it's important to include filtering information when publishing a new message. The meta field isn't included in the payload itself but allows other clients to filter on the supplied information.

To include meta, prepare the data dictionary and pass it to the publishing function as the following example.

var metaPayload = { 
	"my": "meta", 
	"name": "PubNub" 
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "hello",
		channel: "ch1", 
		meta: metaPayload
	},
	onResponse
)

With the meta information being published on publish, you can now leverage the stream filtering to omit messages that aren't important for a particular client.

 Always set the UUID to uniquely identify the user or device that connects to PubNub. This UUID should be persisted, and should remain unchanged for the lifetime of the user or the device. Not setting the UUID can significantly impact your billing if your account uses the Monthly Active Users (MAUs) based pricing model, and can also lead to unexpected behavior if you have Presence enabled.
var pubnub = new PubNub({
    subscribeKey: "myKey",
    uuid: "myUniqueUUID"
});

pubnub.setFilterExpression("filter=expression");

Setting a filter applies to all channels that you will subscribe to from that particular client. This client filter excludes messages that have this subscriber's UUID set at the sender's UUID:

 Always set the UUID to uniquely identify the user or device that connects to PubNub. This UUID should be persisted, and should remain unchanged for the lifetime of the user or the device. Not setting the UUID can significantly impact your billing if your account uses the Monthly Active Users (MAUs) based pricing model, and can also lead to unexpected behavior if you have Presence enabled.
var pubnub = new PubNub({ 
    subscribeKey: "myKey",
    publishKey:"myPubKey",
    uuid: "myUniqueUUID"
});

var filterExprStr = "uuid != '" + pubnub.getUUID() + "'";
pubnub.setFilterExpression(filterExprStr);

When publishing messages, you need to include the sender's UUID if you want the subscriber side client filter to work:

 Always set the UUID to uniquely identify the user or device that connects to PubNub. This UUID should be persisted, and should remain unchanged for the lifetime of the user or the device. Not setting the UUID can significantly impact your billing if your account uses the Monthly Active Users (MAUs) based pricing model, and can also lead to unexpected behavior if you have Presence enabled.
var pubnub = new PubNub({
    subscribeKey: "myKey",
    publishKey: "myPubKey",
    uuid: "myUniqueUUID"
});

var metaPayload = {
    "uuid": pubnub.getUUID() 
}
 
var onResponse = function(status, response) {
    // handle response here.
}
 
pubnub.publish(
    {
        message: "Bonjour",
        channel: "ch1", 
        meta: metaPayload 
    },
    onResponse
)

For the second example, publish the locale for which the published message was generated and allow the client to only receive languages in a specific language.

When publishing, the client uses the meta field to publish:

var metaPayload = { 
	"language": "english"
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "hello", 
		channel: "ch1", 
		meta: metaPayload 
	},
	onResponse
)

On the subscriber side, the filter expression is specified to make sure only english messages will come to the subscriber.

 Always set the UUID to uniquely identify the user or device that connects to PubNub. This UUID should be persisted, and should remain unchanged for the lifetime of the user or the device. Not setting the UUID can significantly impact your billing if your account uses the Monthly Active Users (MAUs) based pricing model, and can also lead to unexpected behavior if you have Presence enabled.
var pubnub = new PubNub({ 
    subscribeKey: "myKey",
    uuid: "myUniqueUUID"
});

pubnub.addListener({
    message: function (message) {
        // handle message
    }
})

pubnub.setFilterExpression("language == 'english'");

Any messages that don't have language=english in the meta won't arrive to the client. For example, the following publish won't be received:

var metaPayload = {
	"language": "french" 
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "Bonjour",
		channel: "ch1", 
		meta: metaPayload 
	},
	onResponse
)

We can improve the second example with support for multiple languages. As the second example we're going to publish in English, French, and Spanish, but receive only French and Spanish.

var metaPayload = {
	"language": "english" 
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "Hi!", 
		channel: "ch1", 
		meta: metaPayload 
	},
	onResponse
)
var metaPayload = { 
	"language": "french" 
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "Bonjour", 
		channel: "ch1",
		meta: metaPayload 
	},
	onResponse
)
var metaPayload = { 
	"language": "spanish" 
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "Hola",
		channel: "ch1",
		meta: metaPayload 
	},
	onResponse
)

On the subscribe side, we're going to use the contains operator to support multiple languages.

Be aware that the contains operator has a very low precedence. When you're using it in a more complex expression, use it with parentheses to ensure it gets evaluated in the way you expect.

 Always set the UUID to uniquely identify the user or device that connects to PubNub. This UUID should be persisted, and should remain unchanged for the lifetime of the user or the device. Not setting the UUID can significantly impact your billing if your account uses the Monthly Active Users (MAUs) based pricing model, and can also lead to unexpected behavior if you have Presence enabled.
var pubnub = new PubNub({ 
    subscribeKey: "myKey",
    uuid: "myUniqueUUID"
});

pubnub.addListener({
    message: function (message) {
        // handle message
    }
})

pubnub.setFilterExpression("('french', 'spanish') contains language");

For the fourth example, we would like to subscribe to all languages except spanish. We begin by publishing similar to example two.

var metaPayload = {
	"language": "english" 
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "Hi!", 
		channel: "ch1",
		meta: metaPayload
	},
	onResponse
)
var metaPayload = {
	"language": "french"
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "Bonjour", 
		channel: "ch1",
		meta: metaPayload 
	},
	onResponse
)
var metaPayload = { 
	"language": "spanish"
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "Hola", 
		channel: "ch1",
		meta: metaPayload
	},
	onResponse
)

On the subscribe side, we're going to use the != operator to reject messages written in spanish.

 Always set the UUID to uniquely identify the user or device that connects to PubNub. This UUID should be persisted, and should remain unchanged for the lifetime of the user or the device. Not setting the UUID can significantly impact your billing if your account uses the Monthly Active Users (MAUs) based pricing model, and can also lead to unexpected behavior if you have Presence enabled.
var pubnub = new PubNub({
    subscribeKey: "myKey",
    uuid: "myUniqueUUID"
});

pubnub.addListener({
    message: function (message) {
        // handle message
    }
})

pubnub.setFilterExpression("language != 'spanish'");
var metaPayload = {
	"price": "99.75",
	"channel": "AAPL"
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "99.75",
		channel: "AAPL",
		meta: metaPayload
	},
	onResponse
)
var metaPayload = {
	"price": "100.10",
	"channel": "AAPL"
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "100.10",
		channel: "AAPL",
		meta: metaPayload
	},
	onResponse
)
var metaPayload = {
	"price": "15.50",
	"channel": "GOOG"
}

var onResponse = function(status, response) {
	// handle response here.
}

pubnub.publish(
	{
		message: "15.50",
		channel: "GOOG",
		meta: metaPayload
	},
	onResponse
)
var metaPayload = {
    "price": "14.95",
    "channel": "GOOG"
}

var onResponse = function(status, response) {
    // handle response here.
}

pubnub.publish(
    {
        message: "14.95",
        channel: "GOOG",
        meta: metaPayload
    },
    onResponse
)
Client filter would be applied to all channels by default, but you could do something like this:
 Always set the UUID to uniquely identify the user or device that connects to PubNub. This UUID should be persisted, and should remain unchanged for the lifetime of the user or the device. Not setting the UUID can significantly impact your billing if your account uses the Monthly Active Users (MAUs) based pricing model, and can also lead to unexpected behavior if you have Presence enabled.
var pubnub = new PubNub({
    subscribeKey: "myKey",
    uuid: "myUniqueUUID"
});

pubnub.addListener({
	message: function (message) {
		// handle message
	}
})

pubnub.setFilterExpression("(price > 100.00 && channel == 'AAPL') || (price < 15.00 && channel == 'GOOG')");

Arithmetic operations are useful when subscribing to stream readings such as temperature. In our example, we're going to publish temperature and only subscribe to events when the temperature is greater than the limit.

var metaPayload = {
    "temperature": 60
}

var onResponse = function(status, response) {
	// handle response here.
}

On the subscriber side, we modify the expression to use the > operator

 Always set the UUID to uniquely identify the user or device that connects to PubNub. This UUID should be persisted, and should remain unchanged for the lifetime of the user or the device. Not setting the UUID can significantly impact your billing if your account uses the Monthly Active Users (MAUs) based pricing model, and can also lead to unexpected behavior if you have Presence enabled.
var pubnub = new PubNub({
    subscribeKey: "myKey",
    uuid: "myUniqueUUID"
});

pubnub.addListener({
	message: function (message) {
		// handle message
	}
})

pubnub.setFilterExpression("temperature > 50");

The filtering language is extensive, and supports advanced use cases:

compound_expression is root

<compound_expression>         ::=   <expression> | <expression> <binary_logical_op> <expression>
<binary_logical_op>           ::=   && | ||
<expression>                  ::=   (<expression>) | <operand> <comparison_operator> <operand> | <unary_logical_op> <operand>
<numeric_comparison_operator> ::=   {==, !=, <, >, <=, >=}
<string_comparison_operator>  ::=   {contains, like}
<unary_logical_op>            ::=   !
<operand>                     ::=   (<operand>) | <unary_op> <operand> | <literals> <binary_op> <literals>
<unary_op>                    ::=   ~
<binary_op>                   ::=   |, &, ^, +, -, /, \*
string == 'match'                 => exact match
string LIKE 'match*'              => LIKE operator: asterisk wildcarding, case insensitive
string LIKE 'match\*'             => LIKE operator: literal match with string containing asterisk character
('Anne','anna','Ann') like 'ann*' => LIKE operator: any of the three set members would be a sufficient match

('a','b','c') CONTAINS string     => Compare against a list of values
otherstring CONTAINS string       => Check for a substring match

(3,5,9) contains numValue         => compare number to a list of values
!((3,5,9) contains numValue)      => Negation

string contains numValue          => str(numValue) in string

numValue > (numA + numB - numC)   => compare number to an arithmetic expression
(numA ^ numB) != (numValue * 10)  => compare 2 expressions
(~numA / numB) <= numValue