cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Capriolo (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13396) Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
Date Fri, 31 Mar 2017 16:25:41 GMT


Edward Capriolo commented on CASSANDRA-13396:

people would complain that C* is slow but don't realize it's in this case because of that

First, its an obvious bug. The entire point of plug-gable logging implementations is so that
you can replace them. 
Second, the only person being actually affected would be Anton, because effective no one else
is changing logging implementations so no one else is hitting that block.

For Anton (and anyone else) they would have to manually change the files in the lib folder
and the configuration. So nothing is 'hidden' to him. He/They make a chance and they can report
if there actually is a performance issue.  

Because they can "scratch their itch" of running Cassandra in a container they might find
new problems or they might make new opportunities. For example, they may find that some other
implementation is actually better or faster. 

If anyone was actually trying to convince be that this bug is intentional, (which is almost
laughable). The proper practice would 

if (!logger instanceof XYZ){
  throw new IllegalArgumentException("we only support XYZ for reasons ABC");

But instead we are attempting to pretend the opposite that the bug is intentional and the
correct thing to do is throw a ClassCastException. 

> Cassandra 3.10: ClassCastException in ThreadAwareSecurityManager
> ----------------------------------------------------------------
>                 Key: CASSANDRA-13396
>                 URL:
>             Project: Cassandra
>          Issue Type: Wish
>            Reporter: Edward Capriolo
>            Priority: Minor

This message was sent by Atlassian JIRA

View raw message