US 9,760,604 B2Granted

System and method for adaptive filtering of data requests

AssigneeGluent Inc.

InventorsAdrian Brian Billington, Paul Robert Bridger, Tanel Poder

Life of this patent

Estimating the term…

Loading patent…

Abstract

This disclosure describes systems and methods related to filtering data requests. In some embodiments, a system may determine an execution plan tree. The system may determine a backend-processed target table in the at least one first storage device. The system may traverse at least one first branch and at least one first node in the execution plan tree. The system may traverse at least one second branch and at least one second node from the parent join node. The system may determine that the rowsource is referenced at the rowsource-access node. The system may determine that the rowsource referenced at the rowsource-access node is a filtered-rowsource. The system may extract at least one join column from a join condition associated with the backend-processed target table and the filtered-rowsource. The system may determine at least one storage location of the filtered-rowsource. The system may determine an adaptive processing path based at least in part on the at least one storage location of the filtered-rowsource, the at least one join column determined from the join condition and the at least one direct predicate determined for the filtered-rowsource. The system may generate at least one target filter predicate for the backend-processed target table.

Claims15

Dependent claims

A system, including:

at least one first server;
at least one first storage device;
at least one memory storing computer-executable instructions;
and
at least one processor configured to access the at least one memory and to execute the computer-executable instructions to:
determine an execution plan tree;
determine a backend-processed target table in the at least one first storage device;
traverse at least one first branch and at least one first node in the execution plan tree until a parent join node of the backend-processed target table referenced by a table-scanning node is reached;
traverse at least one second branch and at least one second node from the parent join node until a rowsource-access node is reached, wherein the rowsource-access node is a root node in the execution plan tree;
determine that the rowsource is referenced at the rowsource-access node;
determine that the rowsource referenced at the rowsource-access node is a filtered-rowsource, wherein the filtered-rowsource is a database table associated with a data structure;
extract at least one join column from a join condition associated with the backend-processed target table and the filtered-rowsource;
determine at least one storage location of the filtered-rowsource;
determine an adaptive processing path based at least in part on the at least one storage location of the filtered-rowsource, the at least one join column determined from the join condition and at least one direct predicate determined for the filtered-rowsource;
and
generate at least one target filter predicate for the backend-processed target table, to filter the backend-processed target table.

13 more elements

A non-transitory computer-readable media storing computer-executable instructions, which when executed by one or more processors cause the one or more processors to perform operations of:

determining an execution plan tree;
determining a backend-processed target table;
traversing at least one first branch and at least one first node in the execution plan tree until a parent join node of the backend-processed target table referenced by a table-scanning node is reached;
traversing at least one second branch and at least one second node from the parent join node until a rowsource-access node is reached, wherein the rowsource-access node is a root node in the execution plan tree;
determining that the rowsource is referenced at the rowsource-access node;
determining that the rowsource referenced at the rowsource-access node is a filtered-rowsource, wherein the filtered-rowsource is a database table associated with a data structure;
extracting at least one join column from a join condition associated with backend-processed target table and the filtered-rowsource;
determining at least one storage location of the filtered-rowsource;
determining an adaptive processing path based at least in part on the at least one storage location of the filtered-rowsource, the at least one join column determined from the join condition and the at least one direct predicate determined for the filtered-rowsource;
and
generating at least one target filter predicate for the backend-processed target table, to filter the backend-processed target table.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application: 15/383,674Filed 19 Dec 2016 · us provisional application
Priority: 23 Dec 2015
Published: US 2017/0185647 A129 Jun 2017
Granted: 12 Sep 2017
Term ends: Not estimatedThe source records don’t support an estimate.

Classification3 codes

G06F 16/24544
Plan optimisation: join order optimisation
G06F 16/9535
Querying, e.g. by the use of web search engines: search customisation based on user profiles and personalisation
G06F
Computing and data processing