ByteYue opened a new pull request, #19284:
URL: https://github.com/apache/doris/pull/19284

   # Proposed changes
   
   Issue Number: close #xxx
   I was writing some regression cases which need call show config action to 
see the config value of BE, but somewhat i found out that one config with type 
bool returned one string `0` or `1`. And in groovy it would parse into false if 
you use `Boolean.parseBoolean(String)`. It confused me a lot and i found out we 
should return correct default value.
   Before this pr:
   
![image](https://user-images.githubusercontent.com/43750022/236250945-e03fe40d-6b0f-4080-a13f-7dc0cf5c40c8.png)
   After this pr:
   
![image](https://user-images.githubusercontent.com/43750022/236251149-d2e80154-95ee-40cc-9f71-d48214f5bf3a.png)
   
   There were some cases which used this action to get config value, luckily 
the wrong parsed value would not influence this cases.
   
![image](https://user-images.githubusercontent.com/43750022/236251630-66923fa0-900e-4141-b8a8-64bfa46d5252.png)
   
   
   ## Problem summary
   
   Describe your changes.
   
   ## Checklist(Required)
   
   * [ ] Does it affect the original behavior
   * [ ] Has unit tests been added
   * [ ] Has document been added or modified
   * [ ] Does it need to update dependencies
   * [ ] Is this PR support rollback (If NO, please explain WHY)
   
   ## Further comments
   
   If this is a relatively large or complex change, kick off the discussion at 
[[email protected]](mailto:[email protected]) by explaining why you 
chose the solution you did and what alternatives you considered, etc...
   
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to