Uploaded image for project: 'Apache Cassandra'
  1. Apache Cassandra
  2. CASSANDRA-300

Enumerate useful consistency options for read/write calls

Agile BoardAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 0.4
    • None
    • None

    Description

      Currently, a user has to specify an int for the number of nodes to block_for. As discussed on IRC, there are only a few options that a user would want, so this would be better encapsulated by an enum.

      enum ConsistencyLevel {
      ZERO = 0,
      ONE = 1,
      QUORUM = 2,
      ALL = 3,
      }

      This could be extended with a fifth option, CUSTOM = 4, if custom specifications are desired
      struct ConsistencyRequest {
      1: required ConsistencyLevel level,
      2: optional int nodes
      }

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            sammy.yu Sammy Yu Assign to me
            euphoria Michael Greene
            Sammy Yu
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment