Extensible language framework using data cartridges

• US 9,058,360 B2
• Filed: 11/30/2010
• Issued: 06/16/2015
• Est. Priority Date: 12/28/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: de Castro Alves, Alexandre, Srinivasan, Anand, Park, Hoyong, Mishra, Shailendra
• Primary Examiner(s): BURKE, JEFF A
• Application Number:
  US12/957,201
• Publication Number:
  US 20110161356A1
• Time in Patent Office: 1,659 Days
• Field of Search: 707/702
• US Class Current: 1/1
• CPC Class Codes: G06F 16/24568 Data stream processing; Continuous queries
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems

Abstract

A framework for extending the capabilities of an event processing system using one or more plug-in components referred to herein as data cartridges. In one set of embodiments, the data cartridge framework described herein can enable an event processing system to support one or more extension languages that are distinct from the native event processing language supported by the system. For example, certain “extension language” data cartridges can be provided that enable an event processing system to support complex data types and associated methods/operations that are common in object-oriented languages, but are not common in event processing languages. In these embodiments, an event processing system can access an extension language data cartridge to compile and execute queries that are written using a combination of the system'"'"'s native event processing language and the extension language.

Claims

1. A method comprising:

receiving, by a computer system, a query expressed in an event processing language, the query including a reference to a complex type implemented in another language distinct from the event processing language; and

compiling, by the computer system, the query by;

retrieving metadata pertaining to the complex type from information stored in a data cartridge for the complex type without requiring definition of a function interface for the complex type using data types that are defined in the event processing language; and

generating, based on the metadata, executable instructions for executing the query;

wherein the reference to the complex type within the query specifies both (a) a class identifier of a class written in said language distinct from the event processing language and (b) a method identifier of a particular method of the class;

wherein the class written in said language distinct from the event processing language includes a plurality of methods that are invocable as complex types referenced in queries expressed in the event processing language; and

wherein the particular method is one of the plurality of methods.

2. The method of claim 1, wherein:

the event processing language is Continuous Query Language (CQL).

3. The method of claim 1, wherein:

the another language distinct from the event processing language is an object-oriented language.

4. The method of claim 1, wherein:

the another language distinct from the event processing language is Java, and wherein the complex type is a Java class.

5. The method of claim 1, wherein:

the query is configured for processing one or more events received via one or more event streams.

6. The method of claim 5 wherein retrieving the metadata pertaining to the complex type comprises:

determining whether the complex type corresponds to an attribute in any of the one or more event streams;

if the complex type does not correspond to an attribute in any of the event streams;

determining whether the complex type corresponds to a type defined in the event processing language; and

if the complex type does not correspond to a type defined in the event processing language, retrieving the metadata pertaining to the complex type from the data cartridge.

7. The method of claim 1, wherein:

the reference to the complex type includes an invocation of the particular method associated with the complex type, and

the invocation includes a name of the particular method and one or more parameters.

8. A system comprising:

a processor configured to;

receive a query expressed in an event processing language, the query including a reference to a complex type implemented in another language distinct from the event processing language; and

compile the query by;

retrieving metadata pertaining to the complex type from information stored in a data cartridge for the complex type without requiring definition of a function interface for the complex type using data types that are defined in the event processing language; and

generating, based on the metadata, executable instructions for executing the query;

wherein the reference to the complex type within the query specifies both (a) a class identifier of a class written in said language distinct from the event processing language and (b) a method identifier of a particular method of the class;

wherein the class written in said language distinct from the event processing language includes a plurality of methods that are invocable as complex types referenced in queries expressed in the event processing language; and

wherein the particular method is one of the plurality of methods.

9. The system of claim 8, wherein:

the reference to the complex type includes an invocation of the particular method associated with the complex type, and

the invocation includes a name of the particular method and one or more parameters.

10. A non-transitory computer-readable storage medium having stored thereon instructions executable by a processor, the instructions comprising:

instructions that cause the processor to receive a query expressed in an event processing language, the query including a reference to a complex type implemented in another language distinct from the event processing language; and

instructions that cause the processor to compile the query by;

retrieving metadata pertaining to the complex type from information stored in a data cartridge for the complex type without requiring definition of a function interface for the complex type using data types that are defined in the event processing language; and

generating, based on the metadata, executable instructions for executing the query;

wherein the reference to the complex type within the query specifies both (a) a class identifier of a class written in said language distinct from the event processing language and (b) a method identifier of a particular method of the class;

wherein the class written in said language distinct from the event processing language includes a plurality of methods that are invocable as complex types referenced in queries expressed in the event processing language; and

wherein the particular method is one of the plurality of methods.

11. The non-transitory computer-readable storage medium of claim 10, wherein:

the reference to the complex type includes an invocation of the particular method associated with the complex type, and

the invocation includes a name of the particular method and one or more parameters.

12. The non-transitory computer-readable storage medium of claim 10, wherein:

the event processing language is Continuous Query Language (CQL).

13. The non-transitory computer-readable storage medium of claim 10, wherein:

the another language distinct from the event processing language is an object-oriented language.

14. The non-transitory computer-readable storage medium of claim 10, wherein:

the another language distinct from the event processing language is Java, and wherein the complex type is a Java class.

15. The non-transitory computer-readable storage medium of claim 10, wherein:

the query is configured for processing one or more events received via one or more event streams.

16. The non-transitory computer-readable storage medium of claim 15, wherein retrieving the metadata pertaining to the complex type comprises:

determining whether the complex type corresponds to an attribute in any of the one or more event streams;

if the complex type does not correspond to an attribute in any of the event streams;

determining whether the complex type corresponds to a type defined in the event processing language; and

if the complex type does not correspond to a type defined in the event processing language, retrieving the metadata pertaining to the complex type from the data cartridge.