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
- 6.2
- 6.1.2

Back Next

unique

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

You cannot reference more than one property for a topic of a rule. The unique operator works with one property for a topic of a rule.

For example, the following rule verifies that three credit card transactions were processed by different merchants:

WHEN 3 transaction t WITH unique(t.Merch_ID) then response

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

WHEN 3 transaction  t WITH unique(t.Merch_ID) AND sum(t.Purchase_Amt) > 500 then response

Consider that two stock topic events have the different symbols, and two bond events have different symbols. The following rule verifies that the stock symbols do not require to be different from the bond symbols:

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

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

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

The unique operator is deprecated. The "distinct" operator replaces the "unique" operator.

Rename Saved Search

Table of Contents

User Guide

User Guide

unique

unique