public abstract class PropertyIndexedEventTable extends Object implements EventTable
MultiKeyUntyped
keys that store the property values.
Takes a list of property names as parameter. Doesn't care which event type the events have as long as the properties exist. If the same event is added twice, the class throws an exception on add.
Modifier and Type | Field and Description |
---|---|
protected EventTableOrganization |
organization |
protected EventPropertyGetter[] |
propertyGetters |
Constructor and Description |
---|
PropertyIndexedEventTable(EventPropertyGetter[] propertyGetters,
EventTableOrganization organization) |
Modifier and Type | Method and Description |
---|---|
void |
add(EventBean[] events,
ExprEvaluatorContext exprEvaluatorContext)
Add an array of events.
|
void |
addRemove(EventBean[] newData,
EventBean[] oldData,
ExprEvaluatorContext exprEvaluatorContext)
Add and remove events from table.
|
protected MultiKeyUntyped |
getMultiKey(EventBean theEvent)
Determine multikey for index access.
|
EventTableOrganization |
getOrganization() |
abstract Set<EventBean> |
lookup(Object[] keys) |
void |
remove(EventBean[] events,
ExprEvaluatorContext exprEvaluatorContext)
Remove events.
|
String |
toQueryPlan() |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
add, clear, destroy, getIndex, getNumberOfEvents, getNumKeys, getProviderClass, isEmpty, iterator, remove
forEach, spliterator
protected final EventPropertyGetter[] propertyGetters
protected final EventTableOrganization organization
public PropertyIndexedEventTable(EventPropertyGetter[] propertyGetters, EventTableOrganization organization)
protected MultiKeyUntyped getMultiKey(EventBean theEvent)
theEvent
- to get properties from for keypublic void addRemove(EventBean[] newData, EventBean[] oldData, ExprEvaluatorContext exprEvaluatorContext)
EventTable
It is up to the index to decide whether to add first and then remove, or whether to remove and then add.
It is important to note that a given event can be in both the removed and the added events. This means that unique indexes probably need to remove first and then add. Most other non-unique indexes will add first and then remove since the an event can be both in the add and the remove stream.
addRemove
in interface EventTable
newData
- to addoldData
- to removeexprEvaluatorContext
- evaluator contextpublic void add(EventBean[] events, ExprEvaluatorContext exprEvaluatorContext)
add
in interface EventTable
events
- to addexprEvaluatorContext
- evaluator contextIllegalArgumentException
- if the event was already existed in the indexpublic void remove(EventBean[] events, ExprEvaluatorContext exprEvaluatorContext)
remove
in interface EventTable
events
- to be removed, can be null instead of an empty array.exprEvaluatorContext
- evaluator contextIllegalArgumentException
- when the event could not be removed as its not in the indexpublic String toQueryPlan()
toQueryPlan
in interface EventTable
public EventTableOrganization getOrganization()
getOrganization
in interface EventTable