System and method for batch query processing
US-2015199404-A1 · Jul 16, 2015 · US
US10127272B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10127272-B2 |
| Application number | US-201615077649-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 22, 2016 |
| Priority date | Mar 22, 2016 |
| Publication date | Nov 13, 2018 |
| Grant date | Nov 13, 2018 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Techniques for modifying a database query are disclosed. A source and/or time associated with an initial database query for execution on a database are determined. A modification of the initial database query is determined based on the source and/or time. The modification includes adding a filter to the initial database query. The modified database query is executed to return a set of results. Optionally, partitions of the database that are relevant to the modified database query may be selected. The modified database query may be executed on only the relevant partitions. The datasets included in the results to the modified database query may be more important, relevant, and/or valuable to a user than the datasets that were excluded based on the filter. The datasets included in the results may be retrieved from faster data storage than the excluded datasets.
Opening claim text (preview).
What is claimed is: 1. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, causes performance of operations comprising: receiving a database query for execution on a database; identifying a source corresponding to the database query; selecting a modification of the database query based on the source; applying the modification to the database query to obtain a modified database query; selecting one or more partitions, from a plurality of partitions of the database, that are relevant to the modified database query based on a partitioning key associated with the database; and executing the modified database query on the selected partitions, without executing the modified database query on the non-selected partitions, to obtain a first set of results. 2. The medium of claim 1 , wherein the database query does not explicitly specify the source. 3. The medium of claim 1 , wherein identifying the source corresponding to the database query comprises: identifying a user or an application that generated the database query. 4. The medium of claim 1 , wherein identifying the source corresponding to the database query comprises: identifying a user or an application from which the database query was received. 5. The medium of claim 1 , wherein selecting the modification of the database query based on the source comprises: executing a function using the source as an input to the function. 6. The medium of claim 1 , wherein selecting the modification of the database query based on the source comprises: mapping the source to one or more criteria to filter the database. 7. The medium of claim 1 , wherein applying the modification to the database query to obtain a modified database query comprises: appending or modifying a filter to the database query. 8. The medium of claim 1 , wherein the operations further comprise: prior to receiving the database query: receiving a selection of a first type of data storage for storing data associated with the source; forming the selected partitions on a first data storage of the first type; and forming the non-selected partitions on a second data storage of a second type different than the first type. 9. The medium of claim 1 , wherein the operations further comprise: prior to receiving the database query: receiving a selection of a first tier of data storage, in a data tiering system, for storing data associated with the source; forming the selected partitions on a first data storage of the first tier; and forming the non-selected partitions on a second data storage of a second tier different than the first tier. 10. The medium of claim 1 , wherein the operations further comprise: prior to receiving the database query: receiving a selection of a first level of compression for storing data associated with the source; forming the selected partitions on a first data storage using the first level of compression; and forming the non-selected partitions on a second data storage using a second level of compression different than the first level of compression. 11. The medium of claim 1 , wherein: the modification to the database query comprises a filter based on one or more criteria specified by a system; and the database query is received from a user interface or application that does not include functionality to generate the filter based on the one or more criteria. 12. The medium of claim 1 , wherein the operations further comprise: prior to receiving the database query: receiving a request to test functionality or performance of a database with a dataset, currently stored in a first partition, being purged from the first partition; and responsive to receiving the request: transferring the dataset from the first partition to a second partition; wherein executing the modified database query does not result in retrieval of the dataset from the second partition. 13. The medium of claim 1 , wherein the operations further comprise: receiving a request to test functionality or performance of a database with a dataset, currently stored in a first partition, being archived to a second partition; responsive to receiving the request: copying the dataset from the first partition to the second partition, without deleting the dataset from the first partition; receiving a second database query for the dataset; applying a modification to the second database query to obtain a modified second database query; executing the modified second database query, wherein executing the modified second database query comprises: determining that the modified second database query is relevant to the second partition and not the first partition; and executing the modified second database query on the second partition. 14. The medium of claim 1 , wherein: the database query does not explicitly specify the source; identifying the source corresponding to the database query comprises: identifying a user that generated the database query; identifying an application that submitted the database query, wherein the application does not include functionality to submit any database queries that filter the database based on a particular criterion; selecting the modification of the database query based on the source comprises: mapping the source to the particular criterion for filtering the database; applying the modification to the database query to obtain a modified database query comprises: appending, to the database query, a filter based on the particular criterion; and the operations further comprise: prior to receiving the database query: receiving a selection of a first type of data storage for storing data associated with the source; forming the selected partitions on a first data storage of the first type; and forming the non-selected partitions on a second data storage of a second type different than the first type. 15. A system, comprising: at least one hardware device including a processor; and the system configured to perform operations comprising: receiving a database query for execution on a database; identifying a source corresponding to the database query; selecting a modification of the database query based on the source; applying the modification to the database query to obtain a modified database query; selecting one or more partitions, from a plurality of partitions of the database, that are relevant to the modified database query based on a partitioning key associated with the database; and executing the modified database query on the selected partitions, without executing the modified database query on the non-selected partitions, to obtain a first set of results. 16. The system of claim 15 , wherein the database query does not explicitly specify the source. 17. The system of claim 15 , wherein identifying the source corresponding to the database query comprises: identifying a user or an application that generated the database query. 18. The system of claim 15 , wherein identifying the source corresponding to the database query comprises: identifying a user or an application from which the database query was received. 19. A method, comprising: receiving a database query for execution on a database; identifying a source corresponding to the database query; selecting a modification of the database query based on the source; applying the modification to the database query to obtain a modified database query; selecting one or more partitions, from a plurality of partitions of the database
General implementation details not specific to a particular type of compression · CPC title
Iterative querying; Query formulation based on the results of a preceding query · CPC title
Physics · mapped topic
Physics · mapped topic
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.