cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bhanu M. Gandikota (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7423) Allow updating individual subfields of UDT
Date Mon, 05 Mar 2018 20:01:00 GMT


Bhanu M. Gandikota commented on CASSANDRA-7423:

Hi I got the following error stack during "nodetool upgrades stables" [from 2.2.5 to 3.11.1].
What do I need to do ?


-bash-4.2$ nodetool upgradesstables

WARN  11:28:28,430 Small cdc volume detected at /cdc_raw; setting cdc_total_space_in_mb to
1982.  You can override this in cassandra.yaml

error: null

-- StackTrace --


at org.apache.cassandra.db.rows.BufferCell.<init>(

at org.apache.cassandra.db.LegacyLayout$CellGrouper.addCell(

at org.apache.cassandra.db.LegacyLayout$CellGrouper.addAtom(

at org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.readRow(

at org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer$UnfilteredIterator.hasNext(

at org.apache.cassandra.db.UnfilteredDeserializer$OldFormatDeserializer.hasNext(





at org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.maybeInit(

at org.apache.cassandra.db.rows.LazilyInitializedUnfilteredRowIterator.isReverseOrder(

at org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$1.reduce(

at org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$1.reduce(

at org.apache.cassandra.utils.MergeIterator$OneToOne.computeNext(

at org.apache.cassandra.utils.AbstractIterator.hasNext(

at org.apache.cassandra.db.partitions.UnfilteredPartitionIterators$2.hasNext(

at org.apache.cassandra.db.transform.BasePartitions.hasNext(

at org.apache.cassandra.db.compaction.CompactionIterator.hasNext(

at org.apache.cassandra.db.compaction.CompactionTask.runMayThrow(


at org.apache.cassandra.db.compaction.CompactionTask.executeInternal(

at org.apache.cassandra.db.compaction.AbstractCompactionTask.execute(

at org.apache.cassandra.db.compaction.CompactionManager$5.execute(

at org.apache.cassandra.db.compaction.CompactionManager$


at java.util.concurrent.ThreadPoolExecutor.runWorker(

at java.util.concurrent.ThreadPoolExecutor$

at org.apache.cassandra.concurrent.NamedThreadFactory.lambda$threadLocalDeallocator$0(



> Allow updating individual subfields of UDT
> ------------------------------------------
>                 Key: CASSANDRA-7423
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Tupshin Harper
>            Assignee: Tyler Hobbs
>            Priority: Major
>              Labels: client-impacting, cql, docs-impacting
>             Fix For: 3.6
> 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

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message