[
https://issues.apache.org/jira/browse/CASSANDRA-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953111#comment-15953111
]
Benjamin Lerer commented on CASSANDRA-13396:
--------------------------------------------
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/[email protected]/msg51603.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
