View-based data mart management system
US-10846284-B1 · Nov 24, 2020 · US
US11461325B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11461325-B2 |
| Application number | US-202117333358-A |
| Country | US |
| Kind code | B2 |
| Filing date | May 28, 2021 |
| Priority date | Jun 1, 2020 |
| Publication date | Oct 4, 2022 |
| Grant date | Oct 4, 2022 |
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.
Embodiments of the present disclosure may provide a dynamic query execution model with fault tolerance and failure recovery techniques. Embodiments of the present disclosure may utilize checkpoints to map processed output files to their corresponding input files. Therefore, if an error occurs in processing one or more files, the system may only need to reschedule processing of selected file(s).
Opening claim text (preview).
What is claimed is: 1. A method comprising: receiving, by one or more processors, an assignment of a batch from a query coordinator, the batch including a group of a set of files from a shared file queue; storing a unique batch ID and information related to the batch in a staging area; performing a first operator on the batch; based on performing the first operator, generating a checkpoint signal; determining a state condition of a second operator as being stateless; based on the stateless condition of the second operator, performing the second operator and passing the checkpoint signal to a third operator without implementing barriers between batches; determining a state condition of the third operator as being non-stateless; based on the non-stateless condition of the third operator, clearing data associated with the third operator, implementing barriers between batches, and performing the third operator; finalizing the stored information in the staging area; generating a materialized result file as an output file associated with the batch; uploading the materialized result file to a storage area from where the materialized result file is accessible to be scanned by the query coordinator; and uploading a listing of the materialized result to an output shared file queue. 2. The method of claim 1 , further comprising: generating a file registration request; transmitting the file registration request to the query coordinator including the unique batch ID indicating that the batch has been processed; and deleting the unique batch ID and information related to the batch stored in the staging area. 3. The method of claim 1 , wherein the first operator includes a table scan operator. 4. The method of claim 1 , wherein the third operator includes an insert operator. 5. The method of claim 1 , wherein the output file includes data corresponding only to the batch and no other batch. 6. A system comprising: one or more processors of a machine; and a memory storing instructions that, when executed by the one or more processors, cause the machine to perform operations comprising: receiving an assignment of a batch an assignment of a batch from a query coordinator, the batch including a group of a set of files from a shared file queue; storing a unique batch ID and information related to the batch in a staging area;; performing a first operator on the batch; based on performing the first operator, generating a checkpoint signal; determining a state condition of a second operator as being stateless; based on the stateless condition of the second operator, performing the second operator and passing the checkpoint signal to a third operator without implementing barriers between batches; determining a state condition of the third operator as being non-stateless; based on the non-stateless condition of the third operator, clearing data associated with the third operator, implementing barriers between batches, and performing the third operator; finalizing the stored information in the staging area; generating a materialized result file as an output file associated with the batch; uploading the materialized result file to a storage area from where the materialized result file is accessible to be scanned by the query coordinator; and uploading a listing of the materialized result to an output shared file queue. 7. The system of claim 6 , the operations further comprising: transmitting the output file associated with the batch; generating a file registration request; and deleting the unique batch ID and information related to the batch. 8. The system of claim 6 , wherein the first operator includes a table scan operator. 9. The system of claim 6 , wherein the third operator includes an insert operator. 10. The system of claim 6 , wherein the output file includes data corresponding only to the batch and no other batch. 11. A machine-storage medium embodying instructions that, when executed by a machine, cause the machine to perform operations comprising: receiving, by one or more processors, an assignment of a batch from a query coordinator, the batch including a group of a set of files from a shared file queue; storing a unique batch ID and information related to the batch in a staging area;; performing a first operator on the batch; based on performing the first operator, generating a checkpoint signal; determining a state condition of a second operator as being stateless; based on the stateless condition of the second operator, performing the second operator and passing the checkpoint signal to a third operator without implementing barriers between batches; determining a state condition of the third operator as being non-stateless; based on the non-stateless condition of the third operator, clearing data associated with the third operator, implementing barriers between batches, and performing the third operator; generating a materialized result file as an output file associated with the batch; uploading the materialized result file to a storage area from where the materialized result file is accessible to be scanned by the query coordinator; and uploading a listing of the materialized result to an output shared file queue. 12. The machine-storage medium of claim 11 , further comprising: transmitting the output file associated with the batch; generating a file registration request; and deleting the unique batch ID and information related to the batch. 13. The machine-storage medium of claim 11 , wherein the first operator includes a table scan operator. 14. The machine-storage medium of claim 11 , wherein the third operator includes an insert operator. 15. The machine-storage medium of claim 11 , wherein the output file includes data corresponding only to the batch and no other batch.
using cached or materialised query results · CPC title
using management policies (point-in-time backing up or restoration of persistent data G06F11/1446; file migration policies for HSM systems G06F16/185) · CPC title
Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455) · CPC title
Plan optimisation · CPC title
Task life-cycle, e.g. stopping, restarting, resuming execution (G06F9/4881 takes precedence) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.