Standardized database connectivity support for an event processing server

• US 8,387,076 B2
• Filed: 07/21/2009
• Issued: 02/26/2013
• Est. Priority Date: 07/21/2009
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Thatte, Mohit, Bishnoi, Sandeep, Jain, Namit, Srinivasan, Anand, Mishra, Shailendra
• Primary Examiner(s): Anya, Charles E
• Application Number:
  US12/506,905
• Publication Number:
  US 20110023055A1
• Time in Patent Office: 1,316 Days
• Field of Search: 707/705, 719/328
• US Class Current: 719/328
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

Techniques for facilitating communication between one or more client applications and an event processing server. In one set of embodiments, a framework is provided that enables a client application to communicate with an event processing server via a standard database connectivity API, such as Java Database Connectivity (JDBC).

Claims

1. A method for facilitating communication between a client application configured to run on a first system and an event processing server configured to run on a second system, the method comprising:

running, on the first system, a database connectivity adapter implementing a database connectivity Application Programming Interface (API), wherein the database connectivity adapter is configured to facilitate communication between the client application and the event processing server via the database connectivity API by;

receiving, in response to an invocation of the database connectivity API by the client application, a query language statement to be executed by the event processing server;

converting the query language statement into a data representation native to the event processing server; and

invoking a procedure native to the event processing server and exposed by the event processing server based on the data representation;

wherein, in converting the query language statement into the data representation native to the event processing server, the database connectivity adapter determines whether a timestamp is specified by the query language statement and performs an action selected from a set of actions based on whether a timestamp is specified in the query language statement;

wherein the set of actions consists of (a) generating a timestamp that is not specified by the query language statement and adding the timestamp to the data representation native to the event processing server and (b) adding, to the data representation native to the event processing server, a timestamp that is specified by the query language statement;

wherein invoking the procedure native to the event processing server causes the event processing server to insert, into an unbounded sequence of events that are ordered by time, a tuple specified within the data representation native to the event processing server.

2. The method of claim 1 wherein the database connectivity API is Java Database Connectivity (JDBC).

3. The method of claim 1 wherein the query language statement is an Continuous Query Language (CQL) statement.

4. The method of claim 3 wherein the query language statement is a CQL statement for inserting data into an event stream.

5. The method of claim 1 wherein parsing the query language statement to determine a type of the statement comprises determining whether the query language statement is a data modification language (DML) statement.

6. The method of claim 5 wherein converting comprises converting one or more data values included in the query language statement into a data representation native to the event processing server in response to determining that the query language statement is a DML statement.

7. The method of claim 6 wherein converting one or more data values included in the query language statement into a data representation native to the event processing server comprises:

determining attribute datatypes for an event stream being modified by the query language statement;

comparing the attribute datatypes to datatypes of the one or more data values; and

if the attribute datatypes and the datatypes of the one or more data values are different but compatible, converting the datatypes of the one or more data values into the attribute datatypes.

8. The method of claim 6 wherein invoking a procedure native to the event processing server and exposed by the event processing server for executing the query language statement comprises invoking a procedure exposed by the event processing server for executing DML statements in response to determining that the query language statement is a DML statement, wherein the procedure takes as an input parameter the data representation of the one or more data values native to the event processing server.

9. The method of claim 1 wherein invoking a procedure exposed by the event processing server for executing the query language statement comprises:

obtaining a reference to a remote object exposed by the event processing server via a remote invocation interface; and

invoking a method of the remote object.

10. The method of claim 9 wherein the remote invocation interface is Java Remote Method Invocation (RMI).

11. The method of claim 1 wherein the client application is a data source configured to generate an event stream.

12. The method of claim 1 wherein the client application is a data integrator configured to aggregate event streams from a plurality of different data sources.

13. A system comprising:

a processing device configured to;

run a client application adapted to interact with an event processing server configured to run on a remote system; and

run a database connectivity adapter implementing a database connectivity API, wherein the database connectivity adapter is configured to facilitate communication between the client application and the event processing server via the database connectivity API by;

receiving, in response to an invocation of the database connectivity API by the client application, a query language statement to be executed by the event processing server;

converting the query language statement into a data representation native to the event processing server; and

invoking a procedure native to the event processing server and exposed by the event processing server based on the data representation;

wherein, in converting the query language statement into the data representation native to the event processing server, the database connectivity adapter determines whether a timestamp is specified by the query language statement and performs an action selected from a set of actions based on whether a timestamp is specified in the query language statement;

wherein the set of actions consists of (a) generating a timestamp that is not specified by the query language statement and adding the timestamp to the data representation native to the event processing server and (b) adding, to the data representation native to the event processing server, a timestamp that is specified by the query language statement;

wherein invoking the procedure native to the event processing server causes the event processing server to insert, into an unbounded sequence of events that are ordered by time, a tuple specified within the data representation native to the event processing server.

14. A non-transitory machine-readable medium having stored thereon program code which, when executed by a processing device of a computer system, causes the processing device to facilitate communication between a client application configured to run on a first system and an event processing server configured to run on a second system, the program code comprising:

code for a database connectivity adapter configured to run on the first system, wherein the database connectivity adapter implements a database connectivity API, and wherein the database connectivity adapter is configured to facilitate communication between the client application and the event processing server via the database connectivity API by;

receiving, in response to an invocation of the database connectivity API by the client application, a query language statement to be executed by the event processing server;

converting the query language statement into a data representation native to the event processing server; and

invoking a procedure native to the event processing server and exposed by the event processing server-based on the data representation;

wherein, in converting the query language statement into the data representation native to the event processing server, the database connectivity adapter determines whether a timestamp is specified by the query language statement and performs an action selected from a set of actions based on whether a timestamp is specified in the query language statement;

wherein the set of actions consists of (a) generating a timestamp that is not specified by the query language statement and adding the timestamp to the data representation native to the event processing server and (b) adding, to the data representation native to the event processing server, a timestamp that is specified by the query language statement;

wherein invoking the procedure native to the event processing server causes the event processing server to insert, into an unbounded sequence of events that are ordered by time, a tuple specified within the data representation native to the event processing server.