Alvin Tan Jian Jia created CASSANDRA-17726:
----------------------------------------------
Summary: Potential Refactoring Estimate
Key: CASSANDRA-17726
URL: https://issues.apache.org/jira/browse/CASSANDRA-17726
Project: Cassandra
Issue Type: Improvement
Reporter: Alvin Tan Jian Jia
Attachments: Cassandra_4.0.4.csv
*Summary*
I have identified a few classes with refactoring potential along with its
estimated time to refactor, specifically BatchlogManager.java. The estimated
time is based on historical commits containing refactoring and the complexity
of the involved classes. The class was refactored once on Jun 12, 2019 along
with other classes in commit 310a48efcfdc0fb77fbd5fd6e734bf17667f617d. Given
the duration of the last refactoring, could it be possible to improve this
class further? I am probably not qualified and experienced enough to point out
the exact code needs to be refactored, given my limited knowledge of the
project and codebase.
*Urgency*
Low priority. For maintenance of code in the long run.
Hi,
I am currently doing some research on Estimating Time Taken for Software
Refactoring. Cassandra is one of my case studies being a highly popular
project. Would appreciate your kind feedback on the appropriateness of the
estimated time to refactor.
I am specifically looking at potential for refactoring, such as breaking
functions that are too long into shorter functions, or to remove code
duplication. Would you agree that there could be some modification to the code
to make it better in the listed classes? And if so, is the estimated time
appropriate to carry out the improvement? I will be grateful for any help you
can provide.
# BatchlogManager.java - 4 hours
# ImmediateExecutor.java - 3 hours
# DatabaseDescriptor.java - 3.5 hours
Thank you.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
