[
https://issues.apache.org/jira/browse/CASSANDRA-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953970#comment-15953970
]
Jeff Jirsa commented on CASSANDRA-13396:
----------------------------------------
{quote}
How does meritocracy work when we spend globs of time striking down patches,
while simultaneously 'ninja fixing' stuff? Go make a patch and get it reviewed
like everyone else.
{quote}
The project has always allowed ninja fixing minor (especially non-code) things.
Comments here are a net positive. There's no reason to fight about adding
comments after the fact.
{quote}
This directly translates to "No one can edit the buggy code I introduced
because THEY might make bugs."
{quote}
Logging a warning for users isn't the same as throwing an exception. It's not
like we're talking about a system property here that requires explicit operator
involvement to even run with another logger, it's logging a single warning
message that bugs may happen and we haven't actively tested other configs. I
don't think that's unreasonable, and it's not "get off my lawn". This isn't an
unreasonable compromise - we don't crash, but we give operators a chance to
know that they're running an untested config.
> 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)
