Composing objects in hosted storage

• US 9,317,523 B2
• Filed: 02/26/2013
• Issued: 04/19/2016
• Est. Priority Date: 02/26/2013
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Google Inc. (Alphabet Inc.)
• Inventors: Aikas, Erkki Ville Juhani, Schwartz, Michael F., Newson, Paul E.
• Primary Examiner(s): Gofman, Alex
• Assistant Examiner(s): Mian, Umar
• Application Number:
  US13/777,632
• Publication Number:
  US 20140244700A1
• Time in Patent Office: 1,148 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 16/176 Support for shared access to files; File sharing support
• CPC Class Codes: G06F 16/182 Distributed file systems
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• 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 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: H04L 63/102 Entity profiles

Abstract

A hosted storage system includes a namespace that contains object identifiers. A first object containing a first data component is stored. A first object identifier in the namespace uniquely identifies the first object. A second object containing a second data component is stored. A second object identifier in the namespace uniquely identifies the second object. A compose object request that designating the first object identifier, the second object identifier, and a third object identifier in the namespace is received. A third object that includes the first data component and the second data component without duplicating the first data component and the second data component is created. The third object identifier is associated with the third object such that the third object identifier uniquely identifies the third object.

Claims

1. A method for composing an object stored in a hosted storage system that includes a namespace that contains object identifiers for objects stored in the hosted storage system, the method comprising:

storing, at the hosted storage system, a first object, the first object including a first data component, wherein a first object identifier in the namespace uniquely identifies the first object in the hosted storage system and enables the first object to be retrieved by a client system over a network;

storing, at the hosted storage system, a second object, the second object including a second data component, wherein a second object identifier in the namespace uniquely identifies the second object in the hosted storage system and enables the second object to be retrieved by a client system over a network;

receiving, at the hosted storage system, a compose object request sent by a client system over a network to the hosted storage system, the compose object request comprises i) a first field for identifying one object to be composed, wherein the first field contains the first object identifier, ii) a second field for identifying another object to be composed, wherein the second field contains the second object identifier, and iii) a third field for identifying the resulting composite object, wherein the third field also contains the first object identifier;

in response to receiving the compose object request, determining i) that the first field contains the first object identifier and ii) that the third field also contains the first object identifier; and

in response to determining i) that the first field contains the first object identifier and ii) that the third field also contains the first object identifier;

creating, in the hosted storage system, a third object that includes the first data component and the second data component without duplicating the first data component and the second data component in the hosted storage system by appending the second data component to the end of the first data component; and

associating, in the hosted storage system, the first object identifier with the third object such that the first object identifier no longer enables the first object to be retrieved by a client system over a network and instead the first object identifier uniquely identifies the third object in the hosted storage system and enables the third object to be retrieved by a client system over a network.

2. The method of claim 1 wherein creating the third object without duplicating the first data component and the second data component in the hosted storage system includes generating metadata that includes a first reference to the first data component and a second reference to the second data component.

3. The method of claim 2 wherein:

the compose request designates an order for the first data object and the second data object in the third object; and

the metadata designates an order for the first reference and the second reference that coincides with the order designated in the compose request.

4. The method of claim 1 comprising maintaining storage of the first object and the second object after creating the third object.

5. The method of claim 4 comprising:

storing, at the hosted storage system, a fourth object, the fourth object including a fourth data component, wherein a fourth object identifier in the namespace uniquely identifies the fourth object in the hosted storage system and enables the fourth object to be retrieved by a client system over a network; and

after creating the third object;

receiving, at the hosted storage system, an additional compose object request sent by a client system over a network to the hosted storage system, the compose object request designating the first object identifier, the fourth object identifier, and a fifth object identifier in the namespace;

in response to receiving the additional compose object request, creating, in the hosted storage system, a fifth object that includes the first data component and the fourth data component; and

associating, in the hosted storage system, the fifth object identifier with the fifth object such that the fifth object identifier uniquely identifies the fifth object in the hosted storage system and enables the fifth object to be retrieved by a client system over a network.

6. The method of claim 4 comprising:

storing, at the hosted storage system, a fourth object, the fourth object including a fourth data component, wherein a fourth object identifier in the namespace uniquely identifies the fourth object in the hosted storage system and enables the fourth object to be retrieved by a client system over a network; and

after creating the third object;

receiving, at the hosted storage system, an additional compose object request sent by a client system over a network to the hosted storage system, the compose object request designating the third object identifier, the fourth object identifier, and a fifth object identifier in the namespace;

in response to receiving the additional compose object request, creating, in the hosted storage system, a fifth object that includes the first data component, the second data component, and the fourth data component; and

associating, in the hosted storage system, the fifth object identifier with the fifth object such that the fifth object identifier uniquely identifies the fifth object in the hosted storage system and enables the fifth object to be retrieved by a client system over a network.

7. The method of claim 1 wherein the first object is associated with a first checksum generated using a composable function and the second object is associated with a second checksum generated using the composable function, the method comprising:

generating a third checksum for the third object based on the first checksum and the second checksum; and

associating the third checksum with the third object.

8. The method of claim 1 wherein the third object identifier is the same as a fourth object identifier for a fourth object, the fourth object being stored in the hosted storage system before the third object is created, the method comprising overwriting the fourth object with the third object.

9. The method of claim 1, wherein the first object is a “

year to date”

log and the second data object is a daily log.

10. A non-transitory computer storage medium storing a computer program, the program comprising instructions that, when executed by one or more processing devices, cause the one or more processing devices to perform a process for composing an object stored in a hosted storage system that includes a namespace that contains object identifiers for objects stored in the hosted storage system, the process comprising:

storing, at the hosted storage system, a first object, the first object including a first data component, wherein a first object identifier in the namespace uniquely identifies the first object in the hosted storage system and enables the first object to be retrieved by a client system over a network;

storing, at the hosted storage system, a second object, the second object including a second data component, wherein a second object identifier in the namespace uniquely identifies the second object in the hosted storage system and enables the second object to be retrieved by a client system over a network;

receiving, at the hosted storage system, a compose object request sent by a client system over a network to the hosted storage system, the compose object request comprises i) a first field for identifying one object to be composed, wherein the first field contains the first object identifier, ii) a second field for identifying another object to be composed, wherein the second field contains the second object identifier, and iii) a third field for identifying the resulting composite object, wherein the third field also contains the first object identifier;

in response to receiving the compose object request, determining i) that the first field contains the first object identifier and ii) that the third field also contains the first object identifier; and

in response to determining i) that the first field contains the first object identifier and ii) that the third field also contains the first object identifier;

creating, in the hosted storage system, a third object that includes the first data component and the second data component without duplicating the first data component and the second data component in the hosted storage system by appending the second data component to the end of the first data component; and

associating, in the hosted storage system, the first object identifier with the third object such that the first object identifier no longer enables the first object to be retrieved by a client system over a network and instead the first object identifier uniquely identifies the third object in the hosted storage system and enables the third object to be retrieved by a client system over a network.

11. The computer storage medium of claim 10, wherein creating the third object without duplicating the first data component and the second data component in the hosted storage system includes generating metadata that includes a first reference to the first data component and a second reference to the second data component.

12. The computer storage medium of claim 11 wherein:

the compose request designates an order for the first data object and the second data object in the third object; and

the metadata designates an order for the first reference and the second reference that coincides with the order designated in the compose request.

13. The computer storage medium of claim 10, the process comprising maintaining storage of the first object and the second object after creating the third object.

14. The computer storage medium of claim 13, the process comprising:

storing, at the hosted storage system, a fourth object, the fourth object including a fourth data component, wherein a fourth object identifier in the namespace uniquely identifies the fourth object in the hosted storage system and enables the fourth object to be retrieved by a client system over a network; and

after creating the third object;

receiving, at the hosted storage system, an additional compose object request sent by a client system over a network to the hosted storage system, the compose object request designating the first object identifier, the fourth object identifier, and a fifth object identifier in the namespace;

in response to receiving the additional compose object request, creating, in the hosted storage system, a fifth object that includes the first data component and the fourth data component; and

associating, in the hosted storage system, the fifth object identifier with the fifth object such that the fifth object identifier uniquely identifies the fifth object in the hosted storage system and enables the fifth object to be retrieved by a client system over a network.

15. The computer storage medium of claim 13, the process comprising:

storing, at the hosted storage system, a fourth object, the fourth object including a fourth data component, wherein a fourth object identifier in the namespace uniquely identifies the fourth object in the hosted storage system and enables the fourth object to be retrieved by a client system over a network; and

after creating the third object;

receiving, at the hosted storage system, an additional compose object request sent by a client system over a network to the hosted storage system, the compose object request designating the third object identifier, the fourth object identifier, and a fifth object identifier in the namespace;

in response to receiving the additional compose object request, creating, in the hosted storage system, a fifth object that includes the first data component, the second data component, and the fourth data component; and

associating, in the hosted storage system, the fifth object identifier with the fifth object such that the fifth object identifier uniquely identifies the fifth object in the hosted storage system and enables the fifth object to be retrieved by a client system over a network.

16. The computer storage medium of claim 10 wherein the first object is associated with a first checksum generated using a composable function and the second object is associated with a second checksum generated using the composable function, the process comprising:

generating a third checksum for the third object based on the first checksum and the second checksum; and

associating the third checksum with the third object.

17. The computer storage medium of claim 10 wherein the third object identifier is the same as a fourth object identifier for a fourth object, the fourth object being stored in the hosted storage system before the third object is created, the process comprising overwriting the fourth object with the third object.

18. The computer storage medium of claim 10, wherein the first object is a “

year to date”

log and the second data object is a daily log.

19. A computer system comprising:

a hosted storage system comprising a processor and computer memory and configured to;

store a first object, the first object including a first data component, wherein a first object identifier in the namespace uniquely identifies the first object in the hosted storage system and enables the first object to be retrieved by a client system over a network;

store a second object, the second object including a second data component, wherein a second object identifier in the namespace uniquely identifies the second object in the hosted storage system and enables the second object to be retrieved by a client system over a network

receiving, at the hosted storage system, a compose object request sent by a client system over a network to the hosted storage system, the compose object request comprises i) a first field for identifying one object to be composed, wherein the first field contains the first object identifier, ii) a second field for identifying another object to be composed, wherein the second field contains the second object identifier, and iii) a third field for identifying the resulting composite object, wherein the third field also contains the first object identifier;

in response to receiving the compose object request, determining i) that the first field contains the first object identifier and ii) that the third field also contains the first object identifier; and

in response to determining i) that the first field contains the first object identifier and ii) that the third field also contains the first object identifier;

creating, in the hosted storage system, a third object that includes the first data component and the second data component without duplicating the first data component and the second data component in the hosted storage system by appending the second data component to the end of the first data component; and

associate the first object identifier with the third object such that the first object identifier no longer enables the first object to be retrieved by a client system over a network and instead the first object identifier uniquely identifies the third object in the hosted storage system and enables the third object to be retrieved by a client system over a network; and

the client system comprising a processor and computer memory and configured to;

send, to the hosted storage system, the compose object request.

20. The system of claim 19 wherein to create the third object without duplicating the first data component and the second data component in the hosted storage system, the hosted storage system is configured to generate metadata that includes a first reference to the first data component and a second reference to the second data component.

21. The system of claim 20 wherein:

the compose request designates an order for the first data object and the second data object in the third object; and

the metadata designates an order for the first reference and the second reference that coincides with the order designated in the compose request.

22. The system of claim 19 wherein the hosted storage system is further configured to maintain storage of the first object and the second object after creating the third object.

23. The system of claim 22 wherein the hosted storage system is further configured to:

store a fourth object, the fourth object including a fourth data component, wherein a fourth object identifier in the namespace uniquely identifies the fourth object in the hosted storage system and enables the fourth object to be retrieved by a client system over a network; and

after creating the third object;

receive an additional compose object request sent by a client system over a network to the hosted storage system, the compose object request designating the first object identifier, the fourth object identifier, and a fifth object identifier in the namespace;

create, in response to receiving the additional compos object request, a fifth object that includes the first data component and the fourth data component; and

associate the fifth object identifier with the fifth object such that the fifth object identifier uniquely identifies the fifth object in the hosted storage system and enables the fifth object to be retrieved by a client system over a network.

24. The system of claim 22 wherein the hosted storage system is further configured to:

store a fourth object, the fourth object including a fourth data component, wherein a fourth object identifier in the namespace uniquely identifies the fourth object in the hosted storage system and enables the fourth object to be retrieved by a client system over a network; and

after creating the third object;

receive an additional compose object request sent by a client system over a network to the hosted storage system, the compose object request designating the third object identifier, the fourth object identifier, and a fifth object identifier in the namespace;

create, in response to receiving the additional compose object request, a fifth object that includes the first data component, the second data component, and the fourth data component; and

associate the fifth object identifier with the fifth object such that the fifth object identifier uniquely identifies the fifth object in the hosted storage system and enables the fifth object to be retrieved by a client system over a network.

25. The system of claim 19 wherein the first object is associated with a first checksum generated using a composable function and the second object is associated with a second checksum generated using the composable function, the hosted storage system configured to:

generate a third checksum for the third object based on the first checksum and the second checksum; and

associate the third checksum with the third object.

26. The system of claim 19 wherein the third object identifier is the same as a fourth object identifier for a fourth object, the fourth object being stored in the hosted storage system before the third object is created, the hosted storage system configured to overwrite the fourth object with the third object.

27. The system of claim 19, wherein the first object is a “

year to date”

log and the second data object is a daily log.