[ 
https://issues.apache.org/jira/browse/CASSANDRA-15876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180831#comment-17180831
 ] 

Ekaterina Dimitrova commented on CASSANDRA-15876:
-------------------------------------------------

[~dcapwell] [~mck]

[Patch 
|https://github.com/ekaterinadimitrova2/cassandra/commit/af64790267e4dad442b429b2a154c2974e9328e3]
 | [JAVA 8 CI 
|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/312/workflows/da4ce69c-e778-467e-b9f3-27ab166a8321]
 [JAVA 11 CI 
|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/312/workflows/0655f3c0-e88c-4b9c-acbe-5d8f084628dc]

There is only one new 
failure(_transient_replication_ring_test.py::TestTransientReplicationRing::test_move_forwards_and_cleanup_).
 I don't find a JIRA ticket or failures in the latest Jenkins reports but I ran 
the test locally both with trunk and my patch - fails in both cases. I will 
open a separate ticket as it is not related to my patch.

I just added one small change 
[here|https://github.com/ekaterinadimitrova2/cassandra/commit/20a9e6ff8a7af179bafe7ecb86163913aa82c6fd]
 and I don't think we need to run CI again, let me know if you disagree with me.

 

> Accessors for SystemProperties
> ------------------------------
>
>                 Key: CASSANDRA-15876
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15876
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Config
>            Reporter: Ekaterina Dimitrova
>            Assignee: Ekaterina Dimitrova
>            Priority: Low
>             Fix For: 4.0, 4.0-beta
>
>
> As part of CASSANDRA-15234, it was suggested a class of accessors for System 
> properties to be created for better clarity and maintainability.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to