[
https://issues.apache.org/jira/browse/HUDI-1300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dugenkui updated HUDI-1300:
---------------------------
Description:
I find that most methods in hudi.StringUtils is easy to be replaced by JDK and
lang3.StringUtils. and there is no special operation in hudi.StringUtils. I
think it would be a good choice to replace hudi.StringUtils with JDK and
lang3.StringUtils.
Another important reason is that the operation of hudi.StringUtils.objToString
is different from Objects.toString(), the user which is used to
Objects.toString() is easy to use StringUtils.objToString by mistake.
was:
I find that most methods in hudi.StringUtils is easy to be replaced by JDK and
lang3.StringUtils. and there is no special operation in hudi.StringUtils. I
think it would be a good choice to remove hudi.StringUtils.
Another important reason is that the operation of hudi.StringUtils.objToString
is different from Objects.toString(), the user which is used to
Objects.toString() is easy to use StringUtils.objToString by mistake.
> Replace org.apache.hudi.common.util.StringUtils with JDK and
> org.apache.commons.lang3.StringUtils
> -------------------------------------------------------------------------------------------------
>
> Key: HUDI-1300
> URL: https://issues.apache.org/jira/browse/HUDI-1300
> Project: Apache Hudi
> Issue Type: Wish
> Reporter: dugenkui
> Priority: Major
>
> I find that most methods in hudi.StringUtils is easy to be replaced by JDK
> and lang3.StringUtils. and there is no special operation in hudi.StringUtils.
> I think it would be a good choice to replace hudi.StringUtils with JDK and
> lang3.StringUtils.
> Another important reason is that the operation of
> hudi.StringUtils.objToString is different from Objects.toString(), the user
> which is used to Objects.toString() is easy to use StringUtils.objToString by
> mistake.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
