gosonzhang opened a new issue, #10066:
URL: https://github.com/apache/inlong/issues/10066

   ### Description
   
   
   
   After using DataProxy for a while, I found that the definition of 
configuration-related keys in CommonConfigHolder.java is not very reasonable. 
Some names are mixed with upper and lower case, some are in camel case, and 
some keys belong to the same type of operation but are not categorized by name, 
etc. In terms of configuration settings, some configurations are too complex, 
making it inconvenient for users.
   
   These issues are not user-friendly and hinder the user experience. I plan to 
optimize the configuration definition based on my usage experience, adjusting 
it according to the categories and themes of usage, such as unifying lowercase, 
separating key names with ".", allowing users to quickly understand which type 
of configuration definition it is based on the name.
   
   However, I also noticed that some of the configuration definitions and usage 
in this class are not settings of the DataProxy node itself but are defined by 
common components. These parts should not be modified but should be adjusted at 
a higher level.
   
   ### InLong Component
   
   InLong DataProxy
   
   ### Are you willing to submit PR?
   
   - [X] Yes, I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@inlong.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to