com.espertech.esper.epl.join.table
Class MultiIndexEventTable

java.lang.Object
  extended by com.espertech.esper.epl.join.table.MultiIndexEventTable
All Implemented Interfaces:
EventTable, java.lang.Iterable<EventBean>

public class MultiIndexEventTable
extends java.lang.Object
implements EventTable

An event table for holding multiple tables for use when multiple indexes of the same dataset must be entered into a cache for use in historical data lookup.

Does not allow iteration, adding and removing events. Does allow clearing all tables and asking for filled or empty tables. All tables are expected to be filled and empty at the same time, reflecting multiple indexes on a single set of data.


Constructor Summary
MultiIndexEventTable(EventTable[] tables)
          Ctor.
 
Method Summary
 void add(EventBean[] events)
          Add events to table.
 void addRemove(EventBean[] newData, EventBean[] oldData)
          Add and remove events from table.
 void clear()
          Clear out index.
 EventTable[] getTables()
          Returns all tables.
 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.
 void remove(EventBean[] events)
          Remove events from table.
 java.lang.String toQueryPlan()
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

MultiIndexEventTable

public MultiIndexEventTable(EventTable[] tables)
Ctor.

Parameters:
tables - tables to hold
Method Detail

getTables

public EventTable[] getTables()
Returns all tables.

Returns:
tables

addRemove

public void addRemove(EventBean[] newData,
                      EventBean[] oldData)
Description copied from interface: EventTable
Add and remove events from table.

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.

Specified by:
addRemove in interface EventTable
Parameters:
newData - to add
oldData - to remove

add

public void add(EventBean[] events)
Description copied from interface: EventTable
Add events to table.

Specified by:
add in interface EventTable
Parameters:
events - to add

remove

public void remove(EventBean[] events)
Description copied from interface: EventTable
Remove events from table.

Specified by:
remove in interface EventTable
Parameters:
events - to remove

iterator

public java.util.Iterator<EventBean> iterator()
Description copied from interface: EventTable
Returns an iterator over events in the table.

Specified by:
iterator in interface EventTable
Specified by:
iterator in interface java.lang.Iterable<EventBean>
Returns:
table iterator

isEmpty

public boolean isEmpty()
Description copied from interface: EventTable
Returns true if the index is empty, or false if not

Specified by:
isEmpty in interface EventTable
Returns:
true for empty index

clear

public void clear()
Description copied from interface: EventTable
Clear out index.

Specified by:
clear in interface EventTable

toQueryPlan

public java.lang.String toQueryPlan()
Specified by:
toQueryPlan in interface EventTable

© 2006-2011 EsperTech Inc.
All rights reserved.
Visit us at espertech.com