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

Using the distinct, group by, and ummatched Filters

The distinct and group by operators filter sets of events before they are processed by a rule. Each of these filtering analytic operators take an argument that specify a single property, which is used as the basis for the filter.

You can specify any number or combination of these operators in a rule. For example, all of the following rules are valid:

when 2 stock s group by s.symbol with ..
when 2 stock s group by s.symbol,s.price with ..

Understanding Filtering Behavior

The filtering behavior for these operators is as follows:

group by. All of the events must have the same value for the specified property.

unmatched. All of events do not have the same value for the specified property, but the values are not required to be unique.

distinct. All of the events must have a different value for the specified property.

For example, consider the following table:

Values	Passes Match	Passes Unique	Passes Unmatched
A	Y	Y	Y
A, B	N	Y	Y
A, A, A	Y	N	N
A, A, B	N	N	Y
A, B, C	N	Y	Y

Rename Saved Search

Table of Contents

User Guide

User Guide

Using the distinct, group by, and ummatched Filters

Using the distinct, group by, and ummatched Filters

Understanding Filtering Behavior