Method and apparatus for eventually consistent delete in a distributed data store
First Claim
Patent Images
1. A method comprising:
- receiving a request from at least one user to delete at least one entry from a distributed data store, wherein the distribute data store includes one or more replicates for the at least one entry;
causing, at least in part, a marking of the at least one entry as deleted without removing the at least one entry, the one or more replicates, or a combination thereof from the distributed data store in response to the request;
causing, at least in part, an initiation of at least one get command for the at least one entry;
determining that there is at least one exception if one or more returned replicates of the at least one entry do not include an identical content value; and
causing, at least in part, a presentation of at least one notification in at least one user interface based, at least in part, on the at least one exception,wherein the at least one entry includes, at least in part, a first field that holds a key, a second field that holds content associated with the key, and a third field that holds version information, andthe marking of the at least one entry includes updating the version information held in the third field.
0 Assignments
0 Petitions
Accused Products
Abstract
Techniques for effective delete operations in a distributed data store with eventually consistent replicated entries include determining to delete a particular entry from the distributed data store. Each entry includes a first field that holds data that indicates a key and a second field that holds data that indicates content associated with the key and a third field that holds data that indicates a version for the content. The method also comprises causing, at least in part, actions that result in marking the particular entry as deleted without removing the particular entry, and updating a version in the third field for the particular entry.
22 Citations
19 Claims
-
1. A method comprising:
-
receiving a request from at least one user to delete at least one entry from a distributed data store, wherein the distribute data store includes one or more replicates for the at least one entry; causing, at least in part, a marking of the at least one entry as deleted without removing the at least one entry, the one or more replicates, or a combination thereof from the distributed data store in response to the request; causing, at least in part, an initiation of at least one get command for the at least one entry; determining that there is at least one exception if one or more returned replicates of the at least one entry do not include an identical content value; and causing, at least in part, a presentation of at least one notification in at least one user interface based, at least in part, on the at least one exception, wherein the at least one entry includes, at least in part, a first field that holds a key, a second field that holds content associated with the key, and a third field that holds version information, and the marking of the at least one entry includes updating the version information held in the third field. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. An apparatus comprising:
-
at least one processor implemented at least partially by hardware; and at least one memory including computer program code for one or more programs, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following, receive a request from at least one user to delete at least one entry from a distributed data store, wherein the distribute data store includes one or more replicates for the at least one entry; cause, at least in part, a marking of the at least one entry as deleted without removing the at least one entry, the one or more replicates, or a combination thereof from the distributed data store in response to the request; cause, at least in part, an initiation of at least one get command for the at least one entry;
praciticabledetermine that there is at least one exception if one or more returned replicates of the at least one entry do not include an identical content value; and cause, at least in part, a presentation of at least one notification in at least one user interface based, at least in part, on the at least one exception, wherein the at least one entry includes, at least in part, a first field that holds a key, a second field that holds content associated with the key, and a third field that holds version information, and the marking of the at least one entry includes updating the version information held in the third field. - View Dependent Claims (10, 11, 12, 13, 14, 15)
-
-
16. A non-transitory computer-readable storage medium carrying one or more sequences of one or more instructions which, when executed by one or more processors, cause an apparatus to at least perform the following steps:
-
receiving a request from at least one user to delete at least one entry from a distributed data store, wherein the distribute data store includes one or more replicates for the at least one entry; causing, at least in part, a marking of the at least one entry as deleted without removing the at least one entry, the one or more replicates, or a combination thereof from the distributed data store in response to the request; causing, at least in part, an initiation of at least one get command for the at least one entry; determining that there is at least one exception if one or more returned replicates of the at least one entry do not include an identical content value; and causing, at least in part, a presentation of at least one notification in at least one user interface based, at least in part, on the at least one exception, wherein the at least one entry includes, at least in part, a first field that holds a key, a second field that holds content associated with the key, and a third field that holds version information, and the marking of the at least one entry includes updating the version information held in the third field. - View Dependent Claims (17, 18, 19)
-
Specification