[
https://issues.apache.org/jira/browse/CASSANDRA-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519787#comment-17519787
]
David Capwell commented on CASSANDRA-17527:
-------------------------------------------
https://app.circleci.com/pipelines/github/dcapwell/cassandra/1337/workflows/48ae2207-68f3-4d67-8d3d-98c2fe009276/jobs/10849
scares me as it was clean (11 expected failures) yesterday... random sample I
see they are all having issues with git, so thats outside of Cassandra project
and in dtest/ccm domain... so ignoring these failures...
> 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]
