[
https://issues.apache.org/jira/browse/CASSANDRA-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15953520#comment-15953520
]
Edward Capriolo edited comment on CASSANDRA-13396 at 4/3/17 2:46 PM:
---------------------------------------------------------------------
{quote}
We can as well state something like "Using any logging library not shipped with
Cassandra is NOT supported. Use at your own risk.". If that is the consensus of
this discussion.
{quote}
-1 The point of this Jira is not to create some new policy to avoid committing
things. Fake blockers like 'this might cause a bug in the future' are not a
valid technical reason to reject something. If that is the case shutdown all
development on everything. I appreciate the attempt to compromise, but this is
not the right direction. "Not supported" puts this in a trigger like situation,
it will create a policy that stop active research. Anyone will be free to
reject further development using the "not supported" argument regardless of how
baseless it is.
was (Author: appodictic):
{quote}
We can as well state something like "Using any logging library not shipped with
Cassandra is NOT supported. Use at your own risk.". If that is the consensus of
this discussion.
{quote}
-1 The point of this Jira is not to create some new policy to avoid committing
things. Fake blockers like 'this might cause a bug in the future' are not a
valid technical reason to reject something. If that is the case shutdown all
development on everything
> 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)
