public class PropertyIndexedEventTable extends java.lang.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.Constructor and Description |
---|
PropertyIndexedEventTable(EventPropertyGetter[] propertyGetters,
EventTableOrganization organization) |
Modifier and Type | Method and Description |
---|---|
void |
add(EventBean[] events)
Add an array of events.
|
void |
addRemove(EventBean[] newData,
EventBean[] oldData)
Add and remove events from table.
|
void |
clear()
Clear out index.
|
java.lang.Object |
getIndex()
Return the index object itself, or an object-array for multiple index structures.
|
java.lang.Integer |
getNumberOfEvents()
If the number of events is readily available, an implementation will return that number
or it may return null to indicate that the count is not readily available.
|
int |
getNumKeys()
If the index retains events using some key-based organization this returns the number of keys,
and may return null to indicate that either the number of keys is not available or
costly to obtain.
|
EventTableOrganization |
getOrganization() |
boolean |
isEmpty()
Returns true if the index is empty, or false if not
|
java.util.Iterator<EventBean> |
iterator()
Returns an iterator over events in the table.
|
java.util.Set<EventBean> |
lookup(java.lang.Object[] keys)
Returns the set of events that have the same property value as the given event.
|
void |
remove(EventBean[] events)
Remove events.
|
java.lang.String |
toQueryPlan() |
public PropertyIndexedEventTable(EventPropertyGetter[] propertyGetters, EventTableOrganization organization)
public void addRemove(EventBean[] newData, EventBean[] oldData)
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 removepublic void add(EventBean[] events)
add
in interface EventTable
events
- to addjava.lang.IllegalArgumentException
- if the event was already existed in the indexpublic void remove(EventBean[] events)
remove
in interface EventTable
events
- to be removed, can be null instead of an empty array.java.lang.IllegalArgumentException
- when the event could not be removed as its not in the indexpublic java.util.Set<EventBean> lookup(java.lang.Object[] keys)
keys
- to compare againstpublic boolean isEmpty()
EventTable
isEmpty
in interface EventTable
public java.util.Iterator<EventBean> iterator()
EventTable
iterator
in interface EventTable
iterator
in interface java.lang.Iterable<EventBean>
public void clear()
EventTable
clear
in interface EventTable
public java.lang.String toQueryPlan()
toQueryPlan
in interface EventTable
public java.lang.Integer getNumberOfEvents()
EventTable
getNumberOfEvents
in interface EventTable
public int getNumKeys()
EventTable
The number returned can be an estimate and may not be accurate.
getNumKeys
in interface EventTable
public java.lang.Object getIndex()
EventTable
May return null if the information is not readily available, i.e. externally maintained index
getIndex
in interface EventTable
public EventTableOrganization getOrganization()
getOrganization
in interface EventTable