[
https://issues.apache.org/jira/browse/CASSANDRA-19656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848673#comment-17848673
]
C. Scott Andreas commented on CASSANDRA-19656:
----------------------------------------------
Brandon, good catch on the upgrade and on revisiting. +1 on proactively
disabling to make sure we don't get surprised in the future.
Would be supportive of revisiting alternate libs in a future major to avoid the
need to explicitly disable as well.
> 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.x, 5.x
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
