Query Object Interfaces

• IDL definition of Query Objects
• C++ header file for Query Objects

A query object serves the dual purposes of communicating to the Storage Manager a user's intent to analyze a particular data set and of providing a means of assessing the impact of a particular analysis upon the data mining and analysis system as well as upon the individual thread of analysis to which the query belongs.

To simultaneously allow users to access information gleaned from the Storage Manager through the query object and to allow the Storage Manager to easily provide this information to the query object in a distributed system, we define two CORBA compliant interfaces:

• smqQueryI
  User-side view of query object used to control and access query object from StAF.
• smqInquisitorI
  Storage Manager-side view of query object used to control and access query object from Storage Manager.

These two interfaces provide related, but distinctly different, modes of access to a single query object. In particular:

• Storage Manager provided attributes
  • smqQueryI provides readonly access to attributes which are provided by the Storage Manager.
    These include:
    • numSeconds - is the current best estimate of the time required to cache all events satisfying the query.
    • numEvents - is the current best estimate of the total number of events which satisfy the query.
    • numEventsCached - is the number of events which satisfy the query which are currently in cache.
    • numEventsDelivered - is the number of events which satisfy the query which have been processed through the cache (including those currently in cache).
    • maxNumEvents - is the lowest upper limit for the total number of events which satisfy the query.
    • minNumEvents - is the highest lower limit for the total number of events which satisfy the query.
    • percentComplete - is a percentage (0.0-100.0) presentation of the numEventsDelivered.
    • state - is the current state of the communication between the query object and the Storage Manager.
  • smqInquisitorI provides read-write access to attributes which are provided by the Storage Manager.
    These include:
    • numSeconds - is the current best estimate of the time required to cache all events satisfying the query.
    • numEvents - is the current best estimate of the total number of events which satisfy the query.
    • numEventsCached - is the number of events which satisfy the query which are currently in cache.
    • numEventsDelivered - is the number of events which satisfy the query which have been delivered to the cache (including those currently in cache).
    • maxNumEvents - is the lowest upper limit for the total number of events which satisfy the query.
    • minNumEvents - is the highest lower limit for the total number of events which satisfy the query.
    • state - is the current state of the communication between the query object and the Storage Manager.
• actions and methods
  • smqQueryI provides methods for actions which the user might take during the course of an analysis.
    These include:
    • abort
    • doFullEstimate
    • doQuickEstimate
    • execute
    • getOidList
    • pause
    • resubmit
    • resume
  • smqInquisitorI provides methods for accessing and modifying the content of the query object.
    These include:
    • setOidList