Dynamic join processing using real time merged notification listener

• US 9,679,006 B2
• Filed: 05/14/2016
• Issued: 06/13/2017
• Est. Priority Date: 05/14/2015
• Status: Active Grant

• Current Assignee: Deephaven Data Labs, LLC
• Original Assignee: Walleye Software LLC
• Inventors: Kent, IV, David R., Zeldis, Mark, Wright, Charles, Caudy, Ryan, Basralian, Raffi, Teodorescu, Radu
• Primary Examiner(s): GOFMAN, ALEX N
• Application Number:
  US15/154,988
• Publication Number:
  US 20160335319A1
• Time in Patent Office: 395 Days
• CPC Class Codes: G06F 11/1451 by selection of backup contents
• CPC Class Codes: G06F 11/1464 for networked environments
• CPC Class Codes: G06F 11/1469 Backup restoration techniques
• CPC Class Codes: G06F 12/0261 using reference counting
• CPC Class Codes: G06F 12/084 with a shared cache
• CPC Class Codes: G06F 12/1483 using an access-table, e.g. matrix or list
• CPC Class Codes: G06F 15/17331 Distributed shared memory [DSM], e.g. remote direct memory access [RDMA]
• CPC Class Codes: G06F 16/113 Details of archiving lifecycle management in storage systems G06F3/0649; backup systems G06F11/1446
• CPC Class Codes: G06F 16/144 Query formulation
• CPC Class Codes: G06F 16/162 Delete operations erasing in storage systems G06F3/0652
• CPC Class Codes: G06F 16/215 Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/221 Column-oriented storage; Management thereof
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/2237 Vectors, bitmaps or matrices
• CPC Class Codes: G06F 16/2246 Trees, e.g. B+trees
• CPC Class Codes: G06F 16/2255 Hash tables
• CPC Class Codes: G06F 16/2264 Multidimensional index structures
• CPC Class Codes: G06F 16/2272 Management thereof
• CPC Class Codes: G06F 16/2282 Tablespace storage structures; Management thereof
• CPC Class Codes: G06F 16/2291 : User-Defined Types; Storage management thereof
• CPC Class Codes: G06F 16/23 : Updating
• CPC Class Codes: G06F 16/2308 : Concurrency control transaction processing G06F9/466
• CPC Class Codes: G06F 16/2358 : Change logging, detection, and notification replication G06F16/27
• CPC Class Codes: G06F 16/2365 : Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2372 : Updates performed during offline database operations
• CPC Class Codes: G06F 16/2379 : Updates performed during online database operations; commit processing
• CPC Class Codes: G06F 16/242 : Query formulation
• CPC Class Codes: G06F 16/2428 : Query predicate definition using graphical user interfaces, including menus and forms G06F16/2423 takes precedence
• CPC Class Codes: G06F 16/245 : Query processing
• CPC Class Codes: G06F 16/2453 : Query optimisation
• CPC Class Codes: G06F 16/24534 : Query rewriting; Transformation
• CPC Class Codes: G06F 16/24535 : of sub-queries or views
• CPC Class Codes: G06F 16/24537 : of operators
• CPC Class Codes: G06F 16/24539 : using cached or materialised query results
• CPC Class Codes: G06F 16/2455 : Query execution
• CPC Class Codes: G06F 16/24553 : of query operations
• CPC Class Codes: G06F 16/2456 : Join operations
• CPC Class Codes: G06F 16/24561 : Intermediate data storage techniques for performance improvement
• CPC Class Codes: G06F 16/2457 : with adaptation to user needs
• CPC Class Codes: G06F 16/24575 : using context
• CPC Class Codes: G06F 16/248 : Presentation of query results
• CPC Class Codes: G06F 16/254 : Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses
• CPC Class Codes: G06F 16/27 : Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/278 : Data partitioning, e.g. horizontal or vertical partitioning
• CPC Class Codes: G06F 16/285 : Clustering or classification
• CPC Class Codes: G06F 16/9024 : Graphs; Linked lists G06F16/9027 takes precedence
• CPC Class Codes: G06F 16/907 : Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
• CPC Class Codes: G06F 16/951 : Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9535 : Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/9538 : Presentation of query results
• CPC Class Codes: G06F 16/9566 : URL specific, e.g. using aliases, detecting broken or misspelled links
• CPC Class Codes: G06F 16/9574 : of access to content, e.g. by caching
• CPC Class Codes: G06F 17/40 : Data acquisition and logging for input to computer G06F3/00
• CPC Class Codes: G06F 21/00 : Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
• CPC Class Codes: G06F 21/6209 : to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
• CPC Class Codes: G06F 2201/805 : Real-time
• CPC Class Codes: G06F 2201/84 : Using snapshots, i.e. a logical point-in-time copy of the data
• CPC Class Codes: G06F 2212/1052 : Security improvement
• CPC Class Codes: G06F 2212/154 : Networked environment
• CPC Class Codes: G06F 2212/163 : Server or database system
• CPC Class Codes: G06F 2212/60 : Details of cache memory
• CPC Class Codes: G06F 3/0481 : based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
• CPC Class Codes: G06F 3/0482 : Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0483 : Interaction with page-structured environments, e.g. book metaphor
• CPC Class Codes: G06F 3/04847 : Interaction techniques to control parameter settings, e.g. interaction with sliders or dials
• CPC Class Codes: G06F 3/0485 : Scrolling or panning
• CPC Class Codes: G06F 3/04895 : Guidance during keyboard input operation, e.g. prompting
• CPC Class Codes: G06F 3/0605 : by facilitating the interaction with a user or administrator
• CPC Class Codes: G06F 3/0656 : Data buffering arrangements
• CPC Class Codes: G06F 3/067 : Distributed or networked storage systems, e.g. storage area networks [SAN], network attached storage [NAS]
• CPC Class Codes: G06F 40/117 : Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/134 : Hyperlinking
• CPC Class Codes: G06F 40/166 : Editing, e.g. inserting or deleting
• CPC Class Codes: G06F 40/174 : Form filling; Merging
• CPC Class Codes: G06F 40/177 : of tables; using ruled lines
• CPC Class Codes: G06F 40/18 : of spreadsheets form-filling G06F40/174
• CPC Class Codes: G06F 40/183 : Tabulation, i.e. one-dimensional positioning
• CPC Class Codes: G06F 40/216 : using statistical methods
• CPC Class Codes: G06F 40/274 : Converting codes to words; Guess-ahead of partial word inputs
• CPC Class Codes: G06F 8/30 : Creation or generation of source code
• CPC Class Codes: G06F 8/41 : Compilation
• CPC Class Codes: G06F 8/427 : Parsing
• CPC Class Codes: G06F 8/60 : Software deployment
• CPC Class Codes: G06Q 40/04 : Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
• CPC Class Codes: H04L 12/18 : for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 51/046 : Interoperability with other network applications or services
• CPC Class Codes: H04L 51/212 : using filtering or selective blocking
• CPC Class Codes: H04L 61/5069 : for group communication, multicast communication or broadcast communication
• CPC Class Codes: H04L 63/101 : Access control lists [ACL]
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 67/01 : Protocols
• CPC Class Codes: H04L 67/1001 : for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/141 : Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/56 : Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/566 : Grouping or aggregating service requests, e.g. for unified processing
• CPC Class Codes: H04L 67/568 : Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5681 : Pre-fetching or pre-delivering data based on network characteristics
• CPC Class Codes: H04L 69/16 : Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

Described are methods, systems and computer readable media for dynamic join operations.

Claims

1. A memory and processor efficient computer system for dynamic updating of join operations, the system comprising:

one or more processors;

computer readable storage coupled to the one or more processors, the computer readable storage having stored thereon instructions that, when executed by the one or more processors, cause the one or more processors to perform operations including;

sending a digital request for a remote query processor from a client computer to a remote query processor on a query server computer;

at the remote query processor, performing operations including;

automatically connecting the client computer to the remote query processor via the digital communications network;

receiving a join-based query digitally from the client computer to the remote query processor that contains two or more input tables to be joined;

adding a node for each table providing input to the join operation to an update propagation graph;

adding a join operation results node to the update propagation graph for holding results of executing the join-based query;

adding a real-time merged notification listener for the join operation node in the update propagation graph;

applying the join operation to the two or more input tables using indexes from the two or more input tables to identify and retrieve data needed for the join operation in order to minimize local memory and processor usage;

using the real-time merged notification listener for the join operation node to listen for any changes to the joined two or more input tables in order to minimize local memory and processor usage by only conducting a join operation when a change has been detected; and

when the real-time merged notification listener receives notification of changes to any of the joined two or more input tables, using indexes from the two or more input tables to apply the join operation only to the changes to update the join operation results node only for changed index ranges in order to minimize local memory and processor usage.

2. The computer system of claim 1, wherein the join-based query is a left_join resulting in a table that has one column for each of a plurality of columns in a first input table'"'"'s columns, and one or more new corresponding second input table columns with names that do not overlap or are renamed in order to not overlap with a name of one or more columns from a first input table;

the one or more new corresponding second input table columns containing an aggregation of all values from the second input table that match a join criteria; and

types of all newly created second input table columns not involved in the join criteria being an array of the second input table'"'"'s column type.

3. The computer system of claim 1, wherein the join-based query is an as_of_join resulting in a table that has one column for each of a plurality of columns in a first input table'"'"'s columns, and one or more new corresponding second input table columns with names that do not overlap or are renamed in order to not overlap with a name of one or more columns from a first input table;

the one or more new columns containing all values from the second input table that match a join criteria, the join criteria performing an exact match on all match columns except for one last match column of the match columns followed by performing a closest-less-than match on the last match column.

4. The computer system of claim 1, wherein the join-based query is a reverse_as_of_join resulting in a table that has one column for each of a plurality of columns in a first input table'"'"'s columns, and one or more new corresponding second input table columns with names that do not overlap or are renamed in order to not overlap with a name of one or more columns from a first input table;

and

the one or more new columns containing all values from the input table that match a join criteria, the join criteria performing an exact match on all match columns except for one last match column of the match columns followed by performing a closest-greater-than match on the last match column.

5. The computer system of claim 1, wherein the join-based query is a range_as_of_join resulting in a table that has one column for each of a plurality of columns in a first input table'"'"'s columns, and one or more new corresponding second input table columns with names that do not overlap or are renamed in order to not overlap with a name of one or more columns from a first input table;

and

the one or more new columns containing all values from the input table that match a join criteria, the join criteria returning each cell in the one or more new columns with an array of all values within a designated range for all match columns except for M match columns of the match columns where the match is exact, and the M match columns define a range match.

6. The computer system of claim 1, wherein the join-based query is a natural_join resulting in a table that has one column for each of a plurality of columns in a first input table'"'"'s columns, and one or more new corresponding second input table columns with names that do not overlap or are renamed in order to not overlap with a name of one or more columns from a first input table;

the table having a same number of rows as the source table, the same number of rows containing an original content of the source table rows; and

the one or more new columns determined by matching one or more values from the input table with the source table.

7. The computer system of claim 1, wherein the join-based query is an exact_join resulting in a table that has one column for each of a plurality of columns in a first input table'"'"'s columns, and one or more new corresponding second input table columns with names that do not overlap or are renamed in order to not overlap with a name of one or more columns from a first input table;

the table having a same number of rows as the source table, the same number of rows containing an original content of the source table rows;

the one or more new columns determined by matching one or more values from the input table with the source table; and

the table containing exactly one match for each row with the input table.

8. The computer system of claim 1, wherein the join-based query creates a subset filtered by a match criteria on a full Cartesian product, resulting in a table that has one column for each of a plurality of columns in a first input table'"'"'s columns, and one or more new corresponding second input table columns with names that do not overlap or are renamed in order to not overlap with a name of one or more columns from a first input table.

9. The computer system of claim 1, wherein the join operation node is different than the join operation results node.

10. The computer system of claim 1, wherein the real-time merged notification listener for the join operation node is separate from the join operation node.

11. The computer system of claim 1, wherein the real-time merged notification listener for the join operation node is separate from the join operation results node.

12. The computer system of claim 1 wherein the operations of the remote query processor further include returning join operation results with strict ordering to guarantee ordering.

13. The computer system of claim 1 wherein the operations of the remote query processor further include returning the join operation results that can contain arrays mapped to data.

14. The computer system of claim 12 wherein the strict ordering is according to time.

15. The computer system of claim 12 wherein the strict ordering is dictated by an order of data in the two or more input tables.

16. The computer system of claim 1, wherein the changes include one or more of an add, modify, delete, or re-index.

17. The computer system of claim 1, wherein the operations of the remote query processor further comprise automatically re-applying the join operation when the real-time merged notification listener detects any one of an add, modify, delete, or re-index message.

18. The computer system of claim 1, further comprising when the two or more input tables are derived from a same ancestor table, changes in the same ancestor table cause a cascade of change notifications through the update propagation graph causing the remote query processor to combine the change notifications for efficiency and consistency.

19. The computer system of claim 17, wherein the automatically re-applying is only applied to changed portions of the two or more input tables and not to unchanged portions.

20. The computer system of claim 2, wherein the join criteria includes a formula.

21. A method for dynamic updating of join operations, the method comprising:

sending a digital request for a remote query processor from a client computer to a remote query processor on a query server computer;

automatically connecting the client computer to the remote query processor via the digital communications network;

receiving a join-based query digitally from the client computer to the remote query processor that contains two or more input tables to be joined;

adding a node for each table providing input to the join operation to an update propagation graph;

adding a join operation results node to the update propagation graph for holding results of executing the join-based query;

adding a real-time merged notification listener for the join operation node in the update propagation graph;

applying the join operation to the two or more input tables using indexes from the two or more input tables to identify and retrieve data needed for the join operation in order to minimize local memory and processor usage;

using the real-time merged notification listener for the join operation node to listen for any changes to the joined two or more input tables in order to minimize local memory and processor usage by only conducting a join operation when a change has been detected; and

when the real-time merged notification listener receives notification of changes to any of the joined two or more input tables, using indexes from the two or more input tables to apply the join operation only to the changes to update the join operation results node only for changed index ranges in order to minimize local memory and processor usage.

22. A nontransitory computer readable medium having stored thereon software instructions that, when executed by one or more processors, cause the one or more processors to perform operations including:

sending a digital request for a remote query processor from a client computer to a remote query processor on a query server computer;

at the remote query processor, performing operations including;

automatically connecting the client computer to the remote query processor via the digital communications network;

receiving a join-based query digitally from the client computer to the remote query processor that contains two or more input tables to be joined;

adding a node for each table providing input to the join operation to an update propagation graph;

adding a join operation results node to the update propagation graph for holding results of executing the join-based query;

adding a real-time merged notification listener for the join operation node in the update propagation graph;

applying the join operation to the two or more input tables using indexes from the two or more input tables to identify and retrieve data needed for the join operation in order to minimize local memory and processor usage;

using the real-time merged notification listener for the join operation node to listen for any changes to the joined two or more input tables in order to minimize local memory and processor usage by only conducting a join operation when a change has been detected; and

when the real-time merged notification listener receives notification of changes to any of the joined two or more input tables, using indexes from the two or more input tables to apply the join operation only to the changes to update the join operation results node only for changed index ranges in order to minimize local memory and processor usage.