[
https://issues.apache.org/jira/browse/CASSANDRA-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17518283#comment-17518283
]
David Capwell commented on CASSANDRA-17527:
-------------------------------------------
Going to wait a bit longer to resolve
https://github.com/apache/cassandra/pull/1552#discussion_r843777579 as the
mailing list hasn't gotten a lot of feedback yet (thanks [~e.dimitrova]); I
agree with the comment, just waiting on feedback
> 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: 2h 10m
> 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]
