[
https://issues.apache.org/jira/browse/CASSANDRA-7682?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14084905#comment-14084905
]
Aleksey Yeschenko commented on CASSANDRA-7682:
----------------------------------------------
bq. Do you create a ticket for addSerializedKeyspace/UDT?
Go ahead and do it, I'll review it quickly (target 2.1.1).
This one, however, I'm going to close w/ Won't Fix. For 3.0, we need entirely
different code (because CASSANDRA-6717), and for 2.1, the potential risk in not
worth the benefit.
The win from making schema mutations more targeted is not from limiting them by
schema change type - it's from increasing the granularity to individual
table/type, continuing where CASSANDRA-7444 stopped.
My plan is to make those changes part of CASSANDRA-6038, since some of those
need protocol changes.
> DefsTable.mergeSchemaInternal improvement
> -----------------------------------------
>
> Key: CASSANDRA-7682
> URL: https://issues.apache.org/jira/browse/CASSANDRA-7682
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Fix For: 2.1.1, 3.0
>
> Attachments: 7682.txt, 7682v2.txt
>
>
> Attached patch only loads
> {{system.schema_keyspaces/schema_columnfamilies/schema_usertypes}} if at
> least one mutation targets such tables.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
