Alvin Tan Jian Jia created HDFS-16643:
-----------------------------------------
Summary: Potential Refactoring
Key: HDFS-16643
URL: https://issues.apache.org/jira/browse/HDFS-16643
Project: Hadoop HDFS
Issue Type: Improvement
Reporter: Alvin Tan Jian Jia
Attachments: Hadoop_release-3.2.2-RC1.csv
*Summary*
I have identified a few classes with refactoring potential, specifically on UI
Components. The issue was refactored once on Jun 25, 2019 along with other
classes in commit ade8d3b60ecdab55bd61a71905ea3dbba0922f3e. Is it possible to
improve UI Components 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. Hadoop 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.
# FederationMBean.java - 4 hours
# NamenodeBeanMetrics.java - 3 hours
# Router.java - 2.5 hours
# RouterMetricsService.java - 1 hour
The attached csv file contains the other recommendations from my research.
Thank you once again for any help you can provide.
Regards,
Alvin
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
