[
https://issues.apache.org/jira/browse/CASSANDRA-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15951093#comment-15951093
]
Robert Stupp commented on CASSANDRA-13396:
------------------------------------------
[~apassiou], right, it's true for any other slf4j binding.
Reason is stuff like CASSANDRA-12535 and CASSANDRA-13173, which are hard to
figure out and even harder to ensure its functionality in unit tests. That's
why I'm against such a change. We cannot foresee the consequences, because we
have not tested other bindings. Even further, the performance implications of
using another logger implementation are not determined. Believe me, it's not
blindly shooting something down - I had a hard time to fix this issue and do
not like to see it happen again. BTW: It's late in the afternoon over here, so
it's not a too quick reaction early in the morning.
> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> ----------------------------------------------------------------
>
> Key: CASSANDRA-13396
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13396
> Project: Cassandra
> Issue Type: Wish
> Reporter: Edward Capriolo
> Assignee: Edward Capriolo
> Priority: Minor
>
> https://www.mail-archive.com/[email protected]/msg51603.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
