[
https://issues.apache.org/jira/browse/CASSANDRA-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519729#comment-17519729
]
David Capwell commented on CASSANDRA-17527:
-------------------------------------------
Starting commit
CI Results (pending):
||Branch||Source||Circle CI||Jenkins||
|trunk|[branch|https://github.com/dcapwell/cassandra/tree/commit_remote_branch/CASSANDRA-17527-trunk-355FBBF4-AD29-4FF0-9433-866CA84399B5]|[build|https://app.circleci.com/pipelines/github/dcapwell/cassandra?branch=commit_remote_branch%2FCASSANDRA-17527-trunk-355FBBF4-AD29-4FF0-9433-866CA84399B5]|[build|https://ci-cassandra.apache.org/job/Cassandra-devbranch/1585/]|
> Clients using JMX are unable to handle non-standard java types but we leak
> this into our interfaces
> ---------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-17527
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17527
> Project: Cassandra
> Issue Type: Bug
> Components: Observability/JMX
> Reporter: David Capwell
> Assignee: David Capwell
> Priority: Normal
> Fix For: 4.1
>
> Time Spent: 3h 20m
> Remaining Estimate: 0h
>
> JMX clients only work if-and-only-if they have the same types defined by the
> interface, so non-standard java (or javax) types should never be used; we
> currently rely on humans to block this in review, which has lead to a few
> interfaces exposing Cassandra types
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
