[CASSANDRA-7423] Allow updating individual subfields of UDT

• Type: Improvement
• Status: Resolved
• Priority: Normal
• Resolution: Fixed
• Fix Version/s: 3.6
• Component/s: Feature/Lightweight Transactions, Legacy/CQL
• Labels: LWT cql
• Impacts: Docs
• Assignee: Tom Hobbs Assign to me
• Reporter: Tupshin Harper

Authors

Tom Hobbs

Reviewers

Benjamin Lerer

• Tester: Philip Thompson
• Created: 20/Jun/14 20:42
• Updated: 07/Nov/19 01:05
• Resolved: 08/Apr/16 23:29

Description

Since user defined types were implemented in CASSANDRA-5590 as blobs (you have to rewrite the entire type in order to make any modifications), they can't be safely used without LWT for any operation that wants to modify a subset of the UDT's fields by any client process that is not authoritative for the entire blob.

When trying to use UDTs to model complex records (particularly with nesting), this is not an exceptional circumstance, this is the totally expected normal situation.

The use of UDTs for anything non-trivial is harmful to either performance or consistency or both.

edit: to clarify, i believe that most potential uses of UDTs should be considered anti-patterns until/unless we have field-level r/w access to individual elements of the UDT, with individual timestamps and standard LWW semantics

Issue Links

• blocks: CASSANDRA-7893 Allow indexing of individual UDT fields
• is related to: CASSANDRA-7826 support non-frozen, nested collections
• is required by: CASSANDRA-6412 Custom creation and merge functions for user-defined column types