You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Alvin Tan Jian Jia (Jira)" <ji...@apache.org> on 2022/06/26 21:48:00 UTC

[jira] [Created] (HIVE-26356) Potential Refactoring

Alvin Tan Jian Jia created HIVE-26356:
-----------------------------------------

             Summary: Potential Refactoring
                 Key: HIVE-26356
                 URL: https://issues.apache.org/jira/browse/HIVE-26356
             Project: Hive
          Issue Type: Improvement
            Reporter: Alvin Tan Jian Jia
         Attachments: Hive_release-0.12.0.csv

*Summary*

I have identified a few classes with refactoring potential, specifically on UDF. The issue was refactored once on Aug 11, 2021  along with other classes in commit 7731b58dc3b1dd6147f1aaf6481e416fa62e4530.  Is it possible to improve UDF 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. Hive 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.
 # GenericUDF.java - 4 hours
 # GenericUDFTimestamp.java - 3 hours

 

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)