Method and apparatus for eventually consistent delete in a distributed data store

US9305002B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9305002-B2
Application numberUS-201514690731-A
CountryUS
Kind codeB2
Filing dateApr 20, 2015
Priority dateMay 22, 2010
Publication dateApr 5, 2016
Grant dateApr 5, 2016

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

What is claimed is: 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. 2. A method of claim 1 , further comprising: causing, at least in part, a generation of at least one prompt to request a determination of at least one correct value for the one or more returned replicates from the at least one user, wherein the at least one notification includes, at least in part, the at least one prompt. 3. A method of claim 2 , further comprising: determining one or more different values for the at least one entry from the one or more returned replicates; and causing, at least in part, a presentation of the one or more different values in the at least one notification for selection of the at least one correct value by the at least one user. 4. A method of claim 1 , further comprising: causing, at least in part, an initiation of a determination of at least one correct value for the one or more returned replicates; and causing, at least in part, a generation of at least one error message if the at least one correct value cannot be determined, wherein the at least one notification includes, at least in part, the at least one error message. 5. A method of claim 4 , wherein the determination of the at least one correct value is based, at least in part, on a quorum of the one or more returned replicates, version information associated with the one or more returned replicates, time stamp information associated with the one or more returned replicates, or a combination thereof. 6. A method of claim 1 , further comprising: determining that one or more returned replicates comprise all of the one or more replicates for the at least one entry and that all of the one or more replicates include the identical content value; and causing, at least in part, a removal of the at least one entry, the one or more replicates, or a combination thereof from the distributed data store. 7. A method of claim 6 , further comprising: causing, at least in part, a transmission of a removal message to one or more nodes of the distributed data store to initiate the removal of the at least one entry, the one or more replicates, or a combination thereof. 8. A method of claim 1 , wherein the causing, at least in part, of the marking of the at least one entry as deleted, includes (a) setting data in a delete flag field of the at least one entry to indicate the at least one entry is to be deleted, or (b) setting data in a size field of the at least one entry to indicate zero size. 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; praciticable determine 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. 10. An apparatus of claim 9 , wherein the apparatus is further caused to: cause, at least in part, a generation of at least one prompt to request a determination of at least one correct value for the one or more returned replicates from the at least one user, wherein the at least one notification includes, at least in part, the at least one prompt. 11. An apparatus of claim 10 , wherein the apparatus is further caused to: determine one or more different values for the at least one entry from the one or more returned replicates; and cause, at least in part, a presentation of the one or more different values in the at least one notification for selection of the at least one correct value by the at least one user. 12. An apparatus of claim 9 , wherein the apparatus is further caused to: cause, at least in part, an initiation of a determination of at least one correct value for the one or more returned replicates; and cause, at least in part, a generation of at least one error message if the at least one correct value cannot be determined, wherein the at least one notification includes, at least in part, the at least one error message. 13. An apparatus of claim 12 , wherein the determination of the at least one correct value is based, at least in part, on a quorum of the one or more returned replicates, version information associated with the one or more returned replicates, time stamp information associated with the one or more returned replicates, or a combination thereof. 14. An apparatus of claim 9 , wherein the apparatus is further caused to: determine that one or more returned replicates comprise all of the one or more replicates for the at least one entry and that all of the one or more replicates include the identical content value; and cause, at least in part, a removal of the at least one entry, the one or more replicates, or a combination thereof from the distributed data store. 15. An apparatus of claim 14 , wherein the apparatus is further caused to: cause, at least in part, a transmission of a removal message to one or more nodes of the distributed data store to initiate the removal of the at least one entry, the one or more replicates, or a combination thereof. 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 fro

Assignees

Inventors

Classifications

  • Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor · CPC title

  • Physics · mapped topic

  • Physics · mapped topic

  • Physics · mapped topic

  • Physics · mapped topic

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9305002B2 cover?
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 indica…
Who is the assignee on this patent?
Nokia Technologies Oy
What technology area does this patent fall under?
Primary CPC classification G06F17/30117. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Apr 05 2016 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).