[
https://issues.apache.org/jira/browse/CASSANDRA-19656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brandon Williams updated CASSANDRA-19656:
-----------------------------------------
Fix Version/s: 5.0-beta2
5.0
5.1
(was: 5.x)
(was: 5.0.x)
Source Control Link:
https://github.com/apache/cassandra/commit/531de93369ac35c18ec9479997c079388dd8d7f2
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Thanks for the review! Committed.
> Revisit disabling chronicle analytics
> -------------------------------------
>
> Key: CASSANDRA-19656
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19656
> Project: Cassandra
> Issue Type: Task
> Components: Local/Other
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 5.0-beta2, 5.0, 5.1
>
>
> We first considered this in CASSANDRA-18538 but determined it wasn't a
> problem. We have upgraded chronicle in CASSANDRA-18049 so we should
> reconfirm with packet analysis that nothing is phoning home, and perhaps
> consider taking further precautions by proactively disabling it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
