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

Upgrade of custom 3.0 version fails with custom 4.0 caused by version parsing logic

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • 4.0-beta2, 4.0
    • Build
    • None

    Description

      In 3.0 and earlier, custom versions could have an extra digit and could have multiple pre release tags separated by -, after upgrading to 4.0 these custom versions no longer are allowed and fail different parts of the code, any place which now uses CassandraVersion.

      The issue is that version was just a String before, so the only parsing rules were controlled by the client, now CassandraVersion is used which is more restrictive.

      To help out, we should allow a "hot fix" digit, and preRelease should allow multiple -

      Attachments

        Activity

          People

            dcapwell David Capwell
            dcapwell David Capwell
            David Capwell
            Brandon Williams, Jon Meredith
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: