[CASSANDRA-13384] Legacy caching options can prevent 3.0 upgrade

• Type: Bug
• Status: Resolved
• Priority: Low
• Resolution: Fixed
• Fix Version/s: 3.0.13, 3.11.0
• Component/s: Legacy/Distributed Metadata
• Severity: Low
• Since Version: 3.0.0
• Assignee: Jeff Jirsa
• Reporter: Jeff Jirsa

Authors

Jeff Jirsa

Reviewers

Jeremiah Jordan

• Created: 28/Mar/17 04:20
• Updated: 16/Apr/19 09:30
• Resolved: 29/Mar/17 00:32

Description

In 2.1, we wrote caching options as a JSONified map, but we tolerated raw strings "ALL", "KEYS_ONLY", "ROWS_ONLY", and "NONE".

If a 2.1 node with any of these strings is upgraded to 3.0, the legacy schema migration will fail.