Cloud Data Ingestion System
US-2023114321-A1 · Apr 13, 2023 · US
US11989200B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11989200-B2 |
| Application number | US-202217872848-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 25, 2022 |
| Priority date | May 25, 2022 |
| Publication date | May 21, 2024 |
| Grant date | May 21, 2024 |
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.
An illustrative embodiment disclosed herein is an apparatus including a processor and a memory. In some embodiments, the memory includes programmed instructions that, when executed by the processor, cause the apparatus to upload an object to a source bucket in an object store and create a lambda bucket in the object store that is symlinked to the source bucket. In some embodiments, the lambda bucket is associated with a predefined transformation. In some embodiments, the memory includes the programmed instructions that, when executed by the processor, cause the apparatus to receive a request to download the object from the lambda bucket, detect that the object is in the source bucket, fetch the object from the source bucket, transform the object, by compute resources of the object store, using the predefined transformation, and download the transformed object.
Opening claim text (preview).
What is claimed: 1. An apparatus comprising a processor and a memory, wherein the memory includes programmed instructions that, when executed by the processor, cause the apparatus to: upload an object to a source bucket in an object store; create a lambda bucket in the object store that is symlinked to the source bucket, wherein the lambda bucket is associated with a predefined transformation; receive a request to download the object from the lambda bucket; in response to uploading the object to the source bucket or updating the object in the source bucket, detect that the object is in the source bucket; fetch the object from the source bucket; and transform the object, by compute resources of the object store, using the predefined transformation; and download the transformed object in response to receiving the request. 2. The apparatus of claim 1 , wherein the memory includes the programmed instructions that, when executed by the processor, cause the apparatus to: cache the transformed object in the lambda bucket; and set a lifecycle policy on the lambda bucket that causes the transformed object to be deleted upon a predefined time elapsing. 3. The apparatus of claim 1 , wherein the memory includes the programmed instructions that, when executed by the processor, further cause the apparatus to: create a second lambda bucket in the object store that is symlinked to the lambda bucket, wherein the second lambda bucket is associated with a second predefined transformation; and transform the transformed object, by the compute resources of the object store, using the second predefined transformation, to generate a second transformed object. 4. The apparatus of claim 1 , wherein the memory includes the programmed instructions that, when executed by the processor, further cause the apparatus to: enable viewing of the transformed object natively in a web browser; and enable editing of the transformed object natively in the web browser. 5. The apparatus of claim 1 , wherein detecting that the object is in the source bucket; fetching the object from the source bucket; transforming the object, by the compute resources of the object store, using the predefined transformation; and downloading the transformed object are in response to receiving the request. 6. The apparatus of claim 1 , wherein the memory includes the programmed instructions that, when executed by the processor, further cause the apparatus to: in response to uploading the object to the source bucket or updating the object in the source bucket, cache the transformed object in the lambda bucket. 7. The apparatus of claim 6 , wherein the memory includes the programmed instructions that, when executed by the processor, further cause the apparatus to: in response to receiving the request to download the transformed object, compare metadata of the object stored in the source bucket to the cached metadata; and in response to determining that the metadata stored in the source bucket is different from the cached metadata, cache, in the lambda bucket, the metadata stored in the source bucket. 8. A non-transitory computer readable storage medium comprising instructions stored thereon that, when executed by a processor, cause the processor to: upload an object to a source bucket in an object store; create a lambda bucket in the object store that is symlinked to the source bucket, wherein the lambda bucket is associated with a predefined transformation; receive a request to download the object from the lambda bucket; in response to uploading the object to the source bucket or updating the object in the source bucket, detect that the object is in the source bucket; fetch the object from the source bucket; and transform the object, by compute resources of the object store, using the predefined transformation; and download the transformed object in response to receiving the request. 9. The medium of claim 8 , comprising the instructions stored thereon that, when executed by the processor, further cause the processor to: cache the transformed object in the lambda bucket; and set a lifecycle policy on the lambda bucket that causes the transformed object to be deleted upon a predefined time elapsing. 10. The medium of claim 8 , comprising the instructions stored thereon that, when executed by the processor, further cause the processor to: create a second lambda bucket in the object store that is symlinked to the lambda bucket, wherein the second lambda bucket is associated with a second predefined transformation; and transform the transformed object, by the compute resources of the object store, using the second predefined transformation, to generate a second transformed object. 11. The medium of claim 8 , comprising the instructions stored thereon that, when executed by the processor, further cause the processor to: enable viewing of the transformed object natively in a web browser; and enable editing of the transformed object natively in the web browser. 12. The medium of claim 8 , wherein detecting that the object is in the source bucket; fetching the object from the source bucket; transforming the object, by the compute resources of the object store, using the predefined transformation; and downloading the transformed object are in response to receiving the request. 13. A computer-implemented method comprising: uploading, by a processor, an object to a source bucket in an object store; creating, by the processor, a lambda bucket in the object store that is symlinked to the source bucket, wherein the lambda bucket is associated with a predefined transformation; receiving, by the processor, a request to download the object from the lambda bucket; in response to uploading the object to the source bucket or updating the object in the source bucket, detecting, by the processor, that the object is in the source bucket; fetching, by the processor, the object from the source bucket; and transforming, by the processor, the object, by compute resources of the object store, using the predefined transformation; and downloading, by the processor, the transformed object in response to receiving the request. 14. The method of claim 13 , further comprising: caching, by the processor, the transformed object in the lambda bucket; and setting, by the processor, a lifecycle policy on the lambda bucket that causes the transformed object to be deleted upon a predefined time elapsing. 15. The method of claim 13 , further comprising: creating, by the processor, a second lambda bucket in the object store that is symlinked to the lambda bucket, wherein the second lambda bucket is associated with a second predefined transformation; and transforming, by the processor, the transformed object, by the compute resources of the object store, using the second predefined transformation, to generate a second transformed object. 16. The method of claim 13 , further comprising: enabling, by the processor, viewing of the transformed object natively in a web browser; and enabling, by the processor, editing of the transformed object natively in the web browser. 17. The method of claim 13 , wherein detecting that the object is in the source bucket; fetching the object from the source bucket; transforming the object, by the compute resources of the object store, using the predefined transformation; and downloading the transformed object are in response to receiving the request.
Data format conversion from or to a database · CPC title
Improving or facilitating administration, e.g. storage management · CPC title
Management of space entities, e.g. partitions, extents, pools · CPC title
Single storage device · CPC title
Large Object storage; Management thereof · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.