[ 
https://issues.apache.org/jira/browse/CASSANDRA-15530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Erick Ramirez updated CASSANDRA-15530:
--------------------------------------
    Test and Documentation Plan: 
{noformat}
$ git diff CASSANDRA-15530..trunk -- CHANGES.txt
diff --git a/CHANGES.txt b/CHANGES.txt
index 37bd517584..396b11a3a2 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -1096,7 +1096,7 @@ Merged from 2.1:
  * Support seek() in EncryptedFileSegmentInputStream (CASSANDRA-11957)
  * SSTable tools mishandling LocalPartitioner (CASSANDRA-12002)
  * When SEPWorker assigned work, set thread name to match pool 
(CASSANDRA-11966)
- * Add cross-DC latency metrics (CASSANDRA-11569)
+ * Add cross-DC latency metrics (CASSANDRA-11596)
  * Allow terms in selection clause (CASSANDRA-10783)
  * Add bind variables to trace (CASSANDRA-11719)
  * Switch counter shards' clock to timestamps (CASSANDRA-9811)
{noformat}
                         Status: Patch Available  (was: In Progress)

Patch is available here -- 
https://github.com/flightc/cassandra/tree/CASSANDRA-15530.

> Update CHANGES.txt with  Add cross-DC latency metrics (CASSANDRA-11569)
> -----------------------------------------------------------------------
>
>                 Key: CASSANDRA-15530
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15530
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Documentation/NEWS.txt
>            Reporter: Erick Ramirez
>            Assignee: Erick Ramirez
>            Priority: Normal
>
> h1. Background
> Question posed on ASF Slack on whether there is a metric for cross-DC 
> latency. I then discovered that there's a typo in {{CHANGES.txt}}.
> h1. Action
> Replace:
> {noformat}
>  * Add cross-DC latency metrics (CASSANDRA-11596)
> {noformat}
> with:
> {noformat}
>  * Add cross-DC latency metrics (CASSANDRA-11569)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to