Page Comparison

...

Realization of the index query system is shown in the class diagram below.

Image RemovedImage Added

Searching the right tree part

...

• is Null
• is not Null
• equals
• not equals
• greater than
• greater or equals than
• less than
• less or equals than
• is in collection
• are all in collection

Since reflection is relatively slow, it was concluded that major performance improvement would be to cache all methods that are invoked. Because of this, IIndexQueryRestirctionProcessor interface is defined, and IndexQuery is simply delegating the checking of all restrictions to the processor.

Updates in version 1.4

There was a need for a extended indexing query class that will provide the needed functionality for the storage tree queering. Because of that the IStorageIndexQuery was defined with three additional properties that can be specified:

1. Exclude IDs - set of the object IDs that will be excluded in the result
2. Include IDs - set of objects that will be included in the result
3. Only invocations without children -  If searching for invocations this flag can be set to specify if the complete objects should be retrieved or their cloned copies without children.

Query providers

The IIndexQueryProvider<E extends IIndexQuery> was introduced, with two implementing classes IndexQueryProvider and StorageIndexQueryProvider. Two problems are solved with providers:

1. Ability to get correctly initialized query objects as the Spring prototype bean
2. Ability to create the query factories that will define the queries need, with no distinction if the query is of the simple or the storage type.

Query factories

As mentioned above the query factories are able to create the proper indexing query without depending if the returning object is IIndexQuery or IStorageIndexQuery. Since the storage services on the UI have to execute the same queries as the ones on the CMR, just with the IStorageIndexQuery objects, the factories were introduces as the on-place where queries will be defined. Later on Spring will bound a StorageIndexQueryProvider to a factory that is producing queries for the storage services. On the other hand Spring will bound a IndexQueryProvider for factories used in the CMR DAO classes.

Need for aggregation

To fully simulate the database queering possibilities for memory storage, aggregation has to be develop in the future, with the set of basic aggregation functions as min, max, avg, sum, etc.