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

protocol v5 duration wire format is overly complex and awkward to implement for clients

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

Details

    • Bug
    • Status: Open
    • Normal
    • Resolution: Unresolved
    • None
    • Legacy/CQL
    • None
    • Normal

    Description

      Protocol V5 defines the duration type to be on the wire as months, days and nanoseconds. Days and months require a timezone to make sense of the duration and varies depending on from which they are applied for.

       

      Go defines a duration type as nanoseconds in int64 which can represent ~290 years. Java duration does not have way to handle months.

       

      I suggest that before 4.0 is release the duration format is converted to just be represented as nanoseconds.

      Attachments

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

          People

            Unassigned Unassigned Assign to me
            Zariel Chris Bannister
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:

              Slack

                Issue deployment