public abstract class PropertyHashedEventTable extends Object implements EventTable
Modifier and Type | Field and Description |
---|---|
protected PropertyHashedEventTableFactory |
factory |
Constructor and Description |
---|
PropertyHashedEventTable(PropertyHashedEventTableFactory factory) |
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 Object |
getKey(EventBean theEvent)
Determine multikey for index access.
|
EventTableOrganization |
getOrganization() |
abstract Set<EventBean> |
lookup(Object key) |
void |
remove(EventBean[] events,
ExprEvaluatorContext exprEvaluatorContext)
Remove events.
|
String |
toQueryPlan() |
String |
toString() |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait
add, clear, destroy, getIndex, getNumberOfEvents, getNumKeys, getProviderClass, isEmpty, iterator, remove
forEach, spliterator
protected final PropertyHashedEventTableFactory factory
public PropertyHashedEventTable(PropertyHashedEventTableFactory factory)
protected Object getKey(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 EventTableOrganization getOrganization()
getOrganization
in interface EventTable
public String toQueryPlan()
toQueryPlan
in interface EventTable
Copyright © 2005–2018. All rights reserved.