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

Index target doesn't correctly recognise non-UTF column names after COMPACT STORAGE drop

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 3.0.16, 3.11.2, 4.0-alpha1, 4.0
    • None
    • None
    • Normal

    Description

      Creating a compact storage table with dynamic composite type, then running ALTER TALBE ... DROP COMPACT STORAGE and then restarting the node will crash Cassandra node, since the Index Target is fetched using hashmap / strict equality. We need to fall back to linear search when index target can't be found (which should not be happening often).

      Attachments

        1. ifesdjeen-14104-3.0-dtest.png
          111 kB
          Alex Petrov
        2. ifesdjeen-14104-3.0-testall.png
          51 kB
          Alex Petrov
        3. ifesdjeen-14104-3.11-dtest.png
          122 kB
          Alex Petrov
        4. ifesdjeen-14104-3.11-testall.png
          18 kB
          Alex Petrov
        5. ifesdjeen-14104-trunk-dtest.png
          165 kB
          Alex Petrov
        6. ifesdjeen-14104-trunk-testall.png
          62 kB
          Alex Petrov

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. CASSANDRA-14468 "Unable to parse targets for index" on upgrade to Cassandra 3.0.10-3.0.16

          • Normal -
          • Resolved

          Activity

            People

              ifesdjeen Alex Petrov
              ifesdjeen Alex Petrov
              Alex Petrov
              Zhao Yang
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: