Preface
RulePoint
RulePoint Concepts
- RulePoint Concepts Overview
- Understanding RulePoint Entities
Using RulePoint
RulePoint Objects
- RulePoint Objects Overview
- State of RulePoint Objects
Working with Topics
Working with Connections
Working with Sources
Working with Responders
Working with Responses
Working with Watchlists
Working with Analytics
- Analytics Overview
- Analytic Types
- Creating an Analytic
- Copying an Analytic
- Editing an Analytic
- Deleting an Analytic
- Viewing Related Objects
- Predefined Analytics
  - abs
  - average
  - ceil
  - charat
  - clean
  - compareto
  - concat
  - confidence
  - correlation
  - count
  - current
  - date
  - datedifference
  - endswith
  - even
  - floor
  - getcurrentdate
  - getdatefrommillis
  - getdateinmillis
  - geodistance
  - geoinbound
  - geoinsidearea
  - geointersect
  - geooutbound
  - geooutsidearea
  - geopassthru
  - indexof
  - integer
  - isblank
  - isholiday
  - isnum
  - istext
  - isweekday
  - isweekend
  - large
  - list2vars
  - lower
  - max
  - min
  - mod
  - mode
  - mround
  - odd
  - parse
  - past
  - percentile
  - power
  - proper
  - range
  - regex
  - replace
  - round
  - rounddown
  - roundup
  - sign
  - small
  - startswith
  - stdev
  - stringequals
  - stringindexof
  - stringlastindexof
  - stringlength
  - substring
  - sum
  - trim
  - truncate
  - upper
  - xpath
- Predefined Operators
  - contains
  - equalsSet
  - has
  - in
  - match
  - notMatch
  - search
  - unique
  - group by
  - distinct
  - unmatched
- Using the distinct, group by, and ummatched Filters
DRQL
Working with Rules
Working with Alerts
Setting Access Controls
Troubleshooting RulePoint Issues
Connecting to an Ultra Messaging Application
Creating an Ultra Messaging JMS Source

User Guide

6.1.2
- 6.2
- 6.1

Back Next

match

The match operator is a unary operator that verifies that all events have the same value for the specified property.

The match operator is useful when dealing with an event set with multiple events where you want to group events by a common property value.

For example, the following rule verifies that three credit card transactions is processed by the same merchant:

WHEN 3 transaction t  WITH match(t.Merchant_ID)  then response

The following rule verifies that three credit card transactions were processed by the same merchant and the total transaction value is greater than $500:

WHEN 3 transaction t WITH match(t.Merchant_ID) AND sum(t.Purchase_Amount)> 500 then response

consider that two stock events have the same symbol, and two bond events have the same symbol. The following rule verifies that the stock symbols do not require to be the same as the bond symbols:

WHEN 2 stock s, 2 bond b WITH match(s.symbol) AND match(b.symbol) then response

The following rule provides the same result using a concatenated syntax:

WHEN 2 stock s, 2 bond b WITH match(s.symbol, b.symbol) then response

The "match" operator is deprecated. The "group by" operator replaces the "match" operator.

Rename Saved Search

Table of Contents

User Guide

User Guide

match

match