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

LegacyLayout does not handle paging states that cross a collection column

Agile BoardAttach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Fix Version/s: 3.0.19
    • Component/s: Messaging/Internode
    • Labels:
      None
    • Bug Category:
      Correctness - Transient Incorrect Response
    • Severity:
      Normal
    • Complexity:
      Low Hanging Fruit
    • Discovered By:
      User Report
    • Platform:
      All
    • Impacts:
      None
    • Since Version:
    • Source Control Link:
    • Test and Documentation Plan:
      Hide

      Two unit tests included

      Show
      Two unit tests included

      Description

      LegacyLayout.decodeBound assumes there is only a single extra component, referring to a column name. In fact an encoded page boundary may include a collection column, and this occurs as a matter of course when paging a table whose last column is a collection.

        Attachments

          Activity
          $i18n.getText('security.level.explanation', $currentSelection) Viewable by All Users
          Cancel

            People

            • Assignee:
              benedict Benedict Elliott Smith Assign to me
              Reporter:
              benedict Benedict Elliott Smith
              Authors:
              Benedict Elliott Smith
              Reviewers:
              Sam Tunnicliffe

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment