Optimistic commit processing for an offline document repository

• US 9,626,379 B1
• Filed: 09/22/2011
• Issued: 04/18/2017
• Est. Priority Date: 09/22/2011
• Status: Expired due to Fees

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Allen, Nicholas A.
• Primary Examiner(s): HUANG, MIRANDA M
• Application Number:
  US13/240,563
• Time in Patent Office: 2,035 Days
• Field of Search: 707608, 707609, 707613, 707615, 707616, 707624, 707625, 707638, 707695, 707E17008, 707999008, 70799901, 707999203
• CPC Class Codes: G06F 16/1873 Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
• CPC Class Codes: G06F 16/219 Managing data history or versioning querying versioned data G06F16/2474; querying temporal data G06F16/2477
• CPC Class Codes: G06F 16/2329 using versioning
• CPC Class Codes: G06F 16/2365 Ensuring data consistency and integrity
• CPC Class Codes: G06F 16/2372 Updates performed during offline database operations
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• 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 40/197 Version control for software G06F8/71

Abstract

A revision request is received at a revision control system that includes a repository identifier, version summary information, and a change description. In response to receiving the revision request, a determination is made as to whether a document repository identified by the repository identifier is active or offline. If the document repository is offline, the version summary information is utilized to determine whether the revision request is probably consistent with current contents of the document repository. If the revision request is probably consistent with the current contents of the document repository, the revision request is placed into a queue, an acceptance message is transmitted in response to the revision request, the document repository is placed into an active state, and the revision request is dequeued and applied to the document repository using the change description.

Claims

1. A revision control system, comprising:

one or more processors; and

one or more memories, the one or more memories having stored thereon instructions that when executed by the one or more processors implement;

a plurality of document repositories that receive revision requests that comprise a change description and apply the revision requests using the change description;

a submission queue that stores revision requests awaiting processing by the document repositories;

a document repository state cache that stores summary information about the document repositories such that a first summary information is about a first document repository and a second summary information is about a second document repository; and

a submission endpoint configured to

receive a first revision request from a first client application and a second revision request from a second client application,

wherein the first revision request comprises a first repository identifier identifying the first document repository, a first version summary information describing an expectation of the first client application of contents of the first document repository prior to the first revision request, and a first change description,

wherein the second revision request comprises a second repository identifier identifying the second document repository, a second version summary information describing an expectation of the second client application of contents of the second document repository prior to the second revision request, and a second change description,

determine that the first document repository and the second document repository are in an offline state,

determine that the first summary information stored in the document repository state cache matches within a specified range the first version summary information received with the first revision request,

determine that the second summary information stored in the document repository state cache does not match within the specified range the second version summary information received with the second revision request,

at least partly in response to the first summary information matching within the specified range the first version summary information, (i) en-queue the first revision request in a submission queue and ii.) transmit a first acceptance message to the first client application, without activating the first document repository, and

at least partly in response to the second summary information not matching within the specified range the second version summary information, (i) activate the second document repository to process the second revision request and (ii) transmit a second acceptance message to the second client application, without placing the second revision request in the submission queue.

2. The system of claim 1, wherein the submission endpoint is further configured to:

determine that the first summary information stored in the document repository state cache exactly matches the first version summary information received with the first revision request.

3. The system of claim 1, wherein the first summary information stored in the document repository state cache and the first version summary information received with the first revision request each comprise a single representation of the contents of the first document repository.

4. The system of claim 1, wherein at least one of:

the first summary information stored in the document repository state cache or the first version summary information received with the first revision request, comprises a plurality of representations of the contents of the first document repository.

5. The system of claim 4, wherein the submission queue is further configured to compare the first summary information stored in the document repository state cache and the first version summary information received with the first revision request in a preferential order.

6. A non-transitory computer-readable storage medium having computer-executable instructions stored thereupon which, when executed by a computer, cause the computer to:

receive a first revision request comprising a first repository identifier, a first version summary information describing an expected contents of a first document repository prior to the first revision request, and a first change description;

receive a second revision request comprising a second repository identifier, a second version summary information describing an expected contents of a second document repository prior to the second revision request, and a second change description;

determine that the first document repository identified by the first repository identifier and the second document repository identified by the second repository identifier are offline;

compare (i) the first version summary information with current contents of the first document repository and (ii) the second version summary information with current contents of the second document repository;

determine that the current contents of the first document repository matches within a specified range the first version summary information received with the first revision request;

determine that the current contents of the second document repository does not match within the specified range the second version summary information received with the second revision request;

place the first revision request in a submission queue and transmit a first acceptance message, without activating the first document repository; and

activate the second document repository to process the second revision request and transmit a second acceptance message, without placing the second revision request in the submission queue.

7. The computer-readable storage medium of claim 6, having further computer-executable instructions stored thereupon which, when executed by the computer, cause the computer to:

place the first document repository into an active state;

remove the first revision request from the submission queue; and

apply the first revision request to the first document repository.

8. The computer-readable storage medium of claim 6, wherein comparing the first version summary information with current contents of the first document repository comprises comparing the first version summary information in the first revision request to summary information for the first document repository stored in a document repository state cache.

9. The computer-readable storage medium of claim 8, wherein the computer-executable instructions stored thereupon which, when executed by the computer, further cause the computer to update the summary information stored in the document repository state cache to reflect contents of the first document repository following application of the first revision request atomically applying the first revision request to the first document repository.

10. The computer-readable storage medium of claim 6, wherein the computer-executable instructions stored thereupon which, when executed by the computer, further cause the computer to update the summary information stored in the document repository state cache based upon the first revision request atomically with placing the first revision request in the submission queue.

11. The computer-readable storage medium of claim 9, wherein the first version summary information in the first revision request and the summary information for the first document repository stored in the document repository state cache each comprise data describing one or more of:

the entire first document repository, one or more files in the first document repository, or a portion of one or more files in the first document repository.

12. The computer-readable storage medium of claim 9, wherein the first version summary information in the first revision request and the summary information for the first document repository stored in the document repository state cache each comprise one or more of:

a version number, a hash value, or a time stamp.

13. The computer-readable storage medium of claim 9, wherein the computer-executable instructions stored thereupon which, when executed by the computer, further cause the computer to store data for use in rolling back the document repository state cache in the event that the first revision request cannot be applied to the document repository.

14. A computer-implemented method for optimistic commit processing for a document repository, the method comprising performing computer-implemented operations for:

receiving a first revision request to revise data in a first document repository that is in an offline state, the first revision request comprising a first version summary information that describes an expected contents of the data requested to be revised;

receiving a second revision request to revise data in a second document repository that is in the offline state, the second revision request comprising a second version summary information that describes an expected contents of the data requested to be revised;

comparing the first version summary information with current contents of the data in the first document repository;

comparing the second version summary information with current contents of the data in the second document repository;

at least partly in response to the current contents of the data in the first document repository not matching within the specified range the first version summary information,

causing the offline first document repository to be placed into an active state,

applying the first revision request to the first document repository once the first document repository has been placed into the active state, and

transmitting a first acceptance message; and

at least partly in response to the current contents of the data in the second document repository matching within the specified range the second version summary information,

placing the second revision request in a submission queue, and

transmitting a second acceptance message, without activating the second document repository.

15. The method of claim 14, wherein the first revision request further comprises a first repository identifier that identifies the first document repository and a first change description that describes a change to be made to the first document repository.

16. The method of claim 15, wherein comparing the first revision request with current contents of the data in the first document repository comprises comparing the first version summary information in the first revision request to a first summary information for the data in the first document repository stored in a document repository state cache.

17. The method of claim 16, wherein the first summary information stored in the document repository state cache and the first version summary information received with the first revision request each comprise a single representation of the current contents of the data.

18. The method of claim 16, wherein at least one of:

the first summary information stored in the document repository state cache or the first version summary information received with the first revision request, comprises a plurality of representations of the current contents of the data, and wherein comparing the first summary information stored in the document repository state cache to the first version summary information received with the revision request comprises comparing the first summary information stored in the first document repository state cache and the first version summary information received with the first revision request in a preferential order.

19. The method of claim 18, wherein the first version summary information in the first revision request and the first summary information for the data stored in the first document repository state cache each comprise one or more of a version number, a hash value, or a time stamp.