You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benjamin Lerer (JIRA)" <ji...@apache.org> on 2017/04/03 08:11:41 UTC
[jira] [Comment Edited] (CASSANDRA-13396) Cassandra 3.10:
ClassCastException in ThreadAwareSecurityManager
[ https://issues.apache.org/jira/browse/CASSANDRA-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953111#comment-15953111 ]
Benjamin Lerer edited comment on CASSANDRA-13396 at 4/3/17 8:10 AM:
--------------------------------------------------------------------
The problem that I see with this ticket is the following: "Once we agree to allow people to use the loggers that they wish we somehow become responsible for the bugs that can show up".
As [~snazy] point it up, some of those issues might be non trivial to figure out. Simply because when someone will open a bug he might not mention that he changed the logging library and we might end up wasting a lot of time to reproduce the problem.
Due to that, I tend to be in favor of Robert suggestion of not supporting it (years spend debugging crappy issues have made me somehow paranoiac).
Now, I think it also make sense to allow people to use another logging library as long as they know that we do not fully support it.
My proposal woud be to log a warning at startup saying that the logging library that they use is not supported.
was (Author: blerer):
The problem that I see with this ticket is the following: "Once we agree to allow people to use the loggers that they wish we somehow become responsible for the bugs that can show up".
As [~snazy] point it up, some of those issues might be non trivial to figure out. Simply because when someone will open a bug he might not mention that he changed the logging library and we might end up wasting a lot of time to reproduce the problem.
Due to that I tend to be in favor of Robert approach (years spend debugging crappy issues have made me somehow paranoiac).
Now, I think it also make sense to allow people to use another logging library as long as they know that we do not fully support it.
My proposal woud be to log a warning at startup saying that the logging library that they use is not supported.
> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> ----------------------------------------------------------------
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
> Issue Type: Bug
> Reporter: Edward Capriolo
> Priority: Minor
>
> https://www.mail-archive.com/user@cassandra.apache.org/msg51603.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)