[
https://issues.apache.org/jira/browse/CASSANDRA-14879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-14879:
---------------------------------------
Description:
People sometimes run into issues with schema, and that is often because they do
concurrent schema changes, which are just not supported and we should fix that
someday, but in the meantime, it's not always easy to even check if you may
indeed have had concurrent schema changes.
A very trivial way to make that easier would be to simply log DDL statements on
the coordinator before they are executed. This is likely useful info for
operators in the first place, and would allow in most case to track if
concurrent schema was the likely cause of a particular issue seen.
+Additional info for newcomers:+
In order to implement this change you will need to modify
{{org.apache.cassandra.cql3.QueryProcessor}} to log the schema change before it
is executed.
was:
People sometimes run into issues with schema, and that is often because they do
concurrent schema changes, which are just not supported and we should fix that
someday, but in the meantime, it's not always easy to even check if you may
indeed have had concurrent schema changes.
A very trivial way to make that easier would be to simply log DDL statements on
the coordinator before they are executed. This is likely useful info for
operators in the first place, and would allow in most case to track if
concurrent schema was the likely cause of a particular issue seen.
> Log DDL statements on coordinator
> ---------------------------------
>
> Key: CASSANDRA-14879
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14879
> Project: Cassandra
> Issue Type: Improvement
> Components: Legacy/CQL
> Reporter: Sylvain Lebresne
> Priority: Low
> Labels: AdventCalendar2021, lhf
> Fix For: 4.x
>
>
> People sometimes run into issues with schema, and that is often because they
> do concurrent schema changes, which are just not supported and we should fix
> that someday, but in the meantime, it's not always easy to even check if you
> may indeed have had concurrent schema changes.
> A very trivial way to make that easier would be to simply log DDL statements
> on the coordinator before they are executed. This is likely useful info for
> operators in the first place, and would allow in most case to track if
> concurrent schema was the likely cause of a particular issue seen.
> +Additional info for newcomers:+
> In order to implement this change you will need to modify
> {{org.apache.cassandra.cql3.QueryProcessor}} to log the schema change before
> it is executed.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
